Which URL, port and weblogic server side settings do I need to use?
It depends if you want to connect to a WebLogic MBean server (Domain, Runtime, Edit) or platform (JDK) MBean server (See MBean Servers).
Connecting with JConsole to a WebLogic MBean server is usually a real pain:
Enable Anonymous Admin Lookup if version is lower than 10.3 (See WebLogic anonymous user permissioning)
Enable IIOP Protocol for Admin Server and Application Servers (See Enable and configure IIOP)
Launch jconsole with a custom commandline (See Managing WebLogic servers with JConsole)
Connecting to platform MBean server is like any other JVM (See How to activate JMX on my JVM for access with jconsole), but you would not see any WebLogic MBeans unless you configure WebLogic to use it (See Registering MBeans in the JVM Platform MBean Server).
Try adding this to your server start-up parameters. Change the port (7011) to whatever you prefer. You should be able to use JConsole then by specifying the remote server "{host}:{port}"
Note: the {host} does not include a "http://" prefix.
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=7011
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
Also, you probably don't want to disable authentication like this in a production environment, but the parameters above should help you with testing. When using this, you won't need to specify a username/password in JConsole.
You'll have to enable the remote server to listen on a specific port for JMX -http://download.oracle.com/javase/1.5.0/docs/guide/management/agent.html#remote
URL would be your server's listen address. You also have the option to require authentication to limit the usage of the debug port.
Related
I am trying to connect JProfiler (10.0.1) to JMX port using quick attach -> another computer.
I can connect to JMX port using jvisualvm and JConsole easily, all I have to do is put in host and port. But on jprofiler I get following error
"Another appliction is running on port 19002. Please check your port
configuration".
I am using oracle JDK jdk1.8.0_181. Below are the JXM options i am using for server startup.
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=19002
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
JProfiler does not connect to profiled JVMs via JMX, the agent opens a server socket on a dedicated port, by default 8849.
If you use quick attach, you do not have to specify a port at all, but select a JVM from a list of running JVMs. For the selected JVM, the profiling agent will be loaded and a port will be assigned automatically in such a way that you do not have to deal with it at all.
I would also recommend to use the latest version, not 10.0.1.
The Server and Client (setclientmode(true)) modes need Java and take quite a while to startup (Ignition.Start). The server is the one that holds the cache. I presume that the client node is like a 'local' copy of the cache.
However, Ignite also supports a ThinClient - where we can 'open a connection' and run queries from Ignite.NET without having Java installed. The only configuration required by a ThinClient is the Host IP Address. How can we connect to a specific grid on the ignite server using the Thin Client?
Is this something that is expected to come in the upcoming releases?
Every server node is listening to some specific port for connections from thin clients. By default this is port 10800, but it can be changed. If this port is occupied, then next available is used.
So, if you want to connect to some specific node, then you should specify its IP and port, that will be used for connection.
Documentation: https://apacheignite-net.readme.io/docs/thin-client#section-configuring-server-nodes
I'm on Weblogic AS 10.3.5, I have two managed servers pointed to a cluster, so I have two url, one for the first managed server, the other one for the second.
I will deploy my application on the cluster, so will I reach it on both the url? will the application deployed and running on both the servers?
How does it work? Can you give me some references, please?
Is it clear?
Thanks a lot!
First, you shouldn't be using WebLogic 10.3.5 anymore since it has reached the last stage of support called Sustained Support. Consider to upgrade at least to WebLogic 10.3.6.
Related to your question, I believe you are talking about a Web Application and how to access it. First you need to read about Load Balancing in a Cluster. For the web part (JSP and Servlets) basically you have to options: setup a Web Server (like Apache HTTP) to make use of the WebLogic Plug-in, that will then be connected to the WebLogic cluster. The other easier option is to simply use an LBR (load balance router hardware).
These are the "software" solutions you have for Load Balancing your web application in a clustered WebLogic:
WebLogic Server supports the following Web servers and associated
proxy plug-ins:
WebLogic Server with the HttpClusterServlet
Netscape Enterprise Server with the Netscape (proxy) plug-in
Apache with the Apache Server (proxy) plug-in
Microsoft Internet Information Server with the Microsoft-IIS (proxy) plug-in
You can read more about this options at the Configure Proxy Plug-ins documentation page for WebLogic 10.3.6.
I am new to the Apache plugin. How can it be configured to detect if my Weblogic server has a valid connection to the datasource and to take it out of the round-robin loop if it doesn't?
If the plugin does not do this is there another way?
Thanks,
Bill
You cant do this using the web server plugin - the plugin is only able to connect to the WLS server and not the database/datasource.
the mechanism you're looking for is to set Test Connection and Retries to the database and it will suspend and retest to an unhealthy connection based on the way its configured.
See more on the Oracle docs.
I have a default Glassfish 3 installation and I am trying to create a secured JMX connection to this server.
I am familiar with adding JVM arguments like:
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=8686
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote. authenticate=true
-Dcom.sun.management.jmxremote.password.file=/usr/SYNCH/PACKT/3166/Chapters_Code/resources/jmxremote.password
-Dcom.sun.management.jmxremote.access.file=/usr/SYNCH/PACKT/3166/Chapters_Code/resources/jmxremote.access
But I am confused by some blogs I see talking about using
asadmin set configs.config.server-config.admin-service.jmx-connector.system.security-enabled=true
to alter the to remove the security-enabled="false" property.
So I want to know:
Does removing security-enabled="false" entry on the make Glassfish use the built-in admin authentication provider? If so, how do I turn that security on so I can access JMX securely?
I am just confused as to what the is suppose to secure against and how to configure more advanced usages.
If the previous question is not correct and/or not possible, then is adding the JVM arguments above the only way to add login security for JMX on glassfish?
Out of the box, when you set a password for the admin user, jmx will require credentials.