How to connect remotely with JConsole to a Coherence managed server in a domain?
(Doc ID 2138903.1)
Last updated on OCTOBER 02, 2024
Applies to:
Oracle Coherence - Version 12.1.2.0.0 and laterInformation in this document applies to any platform.
Goal
Customer is aware of running the Coherence MBeanConnector as the management node with Coherence standalone clusters to access remotely Coherence MBeans tree with JConsole. The JConsole URL is (service:jmx:rmi://xxx.xxx.xxx.xxx:xxxx/jndi/rmi://xxx.xxx.xxx.xxx:xxxx/server)
Customer is having Coherence Managed Servers running in a WebLogic domain and having troubles to access Coherence MBeans tree remotely with JConsole.
Coherence MBeans tree is available when JConsole connecting directly (local connection) to a weblogic coherence managed server or JVisualVM connecting to Weblogic Admin Server using domain Mbean server URL - service:jmx:iiop://xxx.xxx.xxx.xxx:7001/jndi/weblogic.management.mbeanservers.domainruntime. But remote option with JConsole, there is no success.
User has used the below system arguments but not able to make a Jconsole remote connection:
- Checked - Is Coherence Management Node option for a managed server.
- Used Server Startup arguments:
-Dtangosol.coherence.management=all
-Dcom.sun.management.jmxremote
-Dtangosol.coherence.management.remote=true
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
-Dtangosol.coherence.management.remote.host=xxx.xxx.xxx.xxx
-Dtangosol.coherence.management.remote.connectionport=xxxx
-Dtangosol.coherence.management.remote.registryport=xxxx
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |
References |