Terracotta Discussion Forums

I have a terracotta instance with a tc-config jmx port setting of 19520. From remote machines I can telnet to that port and get jmx related binary responses.

However, when trying to connect from jconsole or other thirdparty jmx clients, I get the following exception... "with a root cause of non-JRMP server at remote endpoint".

error connecting to server:Failed to connect to service:jmx:rmi:///jndi/rmi://10.200.12.233:19520/jmxrmi [Nested Exception: java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: non-JRMP server at remote endpoint]]

I have tried several mutations of connect URL's from jconsole -- all without specifying login credentials. (e.g., service:jmx:jmxmp://10.200.12.233:19520)

I can however connect via process id from a jconsole on the machine running the terracotta instance. It appears to be a problem for me only from remote machine. The dev-console can connect just fine.

using terracotta-3.0.1

server section of tc-config.xml
<dso-port>19510</dso-port>
<jmx-port>19520</jmx-port>
<l2-group-port>19530</l2-group-port>

snippet from terracotta server logs
[main] INFO com.terracottatech.console - JMX Server started. Available at URL[service:jmx:jmxmp://0.0.0.0:19520]

I did notice that com.sun.management.jmxremote was not set to anything other than empty string. Unless the reason it is listed in the SystemProperties is that it is set and not null.

[main] INFO com.tc.logging.TCLogging - All Java System Properties for this Terracotta instance:
========================================================================
cluster-forceshutdown : true
com.sun.management.jmxremote :

I think you see tc.jar in your classpath.

jconsole -J-Djava.class.path=JAVA_HOME/lib/jconsole.jar:JAVA_HOME/lib/tools.jar:TC_HOME/lib/tc.jar

Hope that helps.

Try this

jconsole -J-Djava.class.path="${TC_INSTALL_DIR}/bin/tc.jar:${JAVA_HOME}/lib/jconsole.jar"
and then click remote process and type
service:jmx:jmxmp://<host>:<jmx-port>

That worked thank you.

Now I need to work on incorporating this concept in the monitor tool we are using which uses a jmx client to attach. But at least I have something to work with.

Is there any other alternative to connecting to the jmx mbean? I can't figure out how to make this work with any other tools (except jconsole noted in the thread).

I need to monitor this remotely. How are people accomplishing this task without running the dev-console?

Is there some other form of URL which would solve this?

You never said exactly what it is you're hoping to monitor.

Any tool that supports jmxmp protocol should be able to connect remotely just like you did with JConsole. Which tool are you using specifically?

Two tools I was using were

* Zenoss via ZenJMX (http://community.zenoss.org/docs/DOC-3396). We use that for monitoring tomcat, activemq, and other JVMs.

* jmxterm - command line jmx browser of sorts (http://wiki.cyclopsgroup.org/jmxterm:manual)

Mainly we wanted to have some nice statistics monitoring in Zenoss to comliment the other jmx stats for tomcat, etc... Requests, Object counts (any session related data), etc...