I am used to running the Coherence MBeanConnector as the management node with Coherence standalone clusters to access remotely with JConsole Coherence MBeans tree. (service:jmx:rmi://xxx.xxx.xxx.xxx:xxxx/jndi/rmi://xxx.xxx.xxx.xxx:xxxx/server)
We are now switching to Coherence Managed Servers running in WebLogic (12.1.3) and I am having a hard time to access Coherence MBeans tree remotely with JConsole.
Locally (direct JConsole connection to PID) or remotely with JVisualVM and conneciting through WL AdminNode (service:jmx:iiop://xxx.xxx.xxx.xxx:7001/jndi/weblogic.management.mbeanservers.domainruntime), it works.
But remotely with JConsole, no success.
I've pretty much thrown in the WL Server Startup arguments textbox all JMX related arguments I know of, without success:
[x] Is Coherence Management Node
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
I have been struggling with this for a while.
Anyone had success with JConsole, remotely and Coherence Managed Servers?