VMware Cloud Community
boris_hyperic
Contributor
Contributor

Unexpected error running autodiscoverer for plugin: Tomcat 5.5:

Hi,

Any suggestion how to resolve Tomcat 5.5 auto-discovery problem? Stack trace is below. Manual discovery will also be OK as long as it works.

If I try to set JMX URL later through UI (Resources -> my_server_name -> Tomcat 5.5 -> Configuration Properties) it gives "Invalid jmxUrl" although I use that URL in JConsole:

The configuration has not been set for this resource due to : Agent error: Invalid jmxUrl service:jmx:rmi:///jndi/rmi://my_server_name:50500/jmxrmi


It then keeps this URL that is definitely wrong: http://::ffff:10.4.68.66:8080

JVM is started with these parameters and JConsole works fine:
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=50500
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false

Thanks in advance,
Boris

2009-03-04 19:35:43,655 ERROR [Thread-3] [RuntimeAutodiscoverer] Unexpected error running autodiscoverer for plugin: Tomcat 5.5: Unable to get MBean info: Invalid JMX URL port: 10.4.68.66
org.hyperic.hq.product.PluginException: Unable to get MBean info: Invalid JMX URL port: 10.4.68.66
at org.hyperic.hq.plugin.servlet.ServletDiscoveryPlugin.getMBeanInfo(ServletDiscoveryPlugin.java:111)
at org.hyperic.hq.plugin.servlet.Tomcat55RuntimeADPlugin.discoverResources(Tomcat55RuntimeADPlugin.java:76)
at org.hyperic.hq.autoinventory.agent.server.RuntimeAutodiscoverer.doRuntimeScan_internal(RuntimeAutodiscoverer.java:272)
at org.hyperic.hq.autoinventory.agent.server.RuntimeAutodiscoverer.doRuntimeScan(RuntimeAutodiscoverer.java:205)
at org.hyperic.hq.autoinventory.ScanManager.mainRunLoop(ScanManager.java:165)
at org.hyperic.hq.autoinventory.ScanManager.access$000(ScanManager.java:41)
at org.hyperic.hq.autoinventory.ScanManager$1.run(ScanManager.java:107)
0 Kudos
2 Replies
boris_hyperic
Contributor
Contributor

P.S. Tomcat is configured for monitoring and the hyperic-hq/jmx-attributes servlet is working fine:

Time: 1236215052124
Remote: xxxxxx
User: null
Server: Apache Tomcat/5.5.25
.......
0 Kudos
boris_hyperic
Contributor
Contributor

The answer is that jmxUrl, jmxUser and jmxPass not related to the JMX communication protocol.

What is called jmxUrl is URL of the root page on the monitored Tomcat server (like http://192.168.0.105:8080).

What is called jmxUser and jmxPass seems Hyperic server authentication (default is hqadmin and hqadmin).

I see your HQ 4.1.0 Beta 3 has same UI for this configuration page. You may want to modify that.
0 Kudos