Description of problem:
I have tomcat 5.5.29 installed and when the agent is started, the tomcat is autodiscoverd. However, the service shows down even if it is up. In log it complains failed to determine version number.
Version-Release number of selected component (if applicable):
jon-server-2.4.0.GA_QA Build# 43.
Steps to Reproduce:
1. Install and configure tomcat 5.5.29. Start the same.
2. Install JON agent.
3. Check the dashboard for the new platform.
4. Check the tomcat under the newly discovered platform.
Autodiscovery works however the service show down with below error in log file,
12:06:58,776 INFO [InventoryManager.discovery-1] (rhq.core.pc.inventory.AutoDiscoveryExecutor)- Process scan auto-detected new server resource: scan=[ProcessScan: query=[process|basename|match=^java.*,arg|org.apache.catalina.startup.Bootstrap|match=.*], name=[Tomcat]], discovered-process=[process: pid=, name=[/root/Desktop/JON/jdk1.6.0_19/bin/java], ppid=]
12:06:58,777 WARN [ResourceDiscoveryComponent.invoker.daemon-2] (jboss.on.plugins.tomcat.TomcatDiscoveryComponent)- DEBUG DEPLOYMENT....
12:06:58,858 WARN [ResourceDiscoveryComponent.invoker.daemon-2] (jboss.on.plugins.tomcat.TomcatDiscoveryComponent)- Failed to determine Tomcat Server Version Given:
12:06:58,861 INFO [InventoryManager.discovery-1] (rhq.core.pc.inventory.InventoryManager)- Detected new Server [Resource[id=0, type=Tomcat Server, key=/root/Desktop/JON/apache-tomcat-5.5.29, name=Tomcat (8080), parent=<null>, version=Unknown Version]] - adding to local inventory...
Version number should be correctly determined and service should show up.
On F-12, the autodiscover did not find tomcat at all. I'll look more into that and open another bug if relevent.
Does this occur with the Tomcat instance bundled with EWS?
Pushing to ON_QA to determine if this is a problem which occurs with Tomcat from EWS
Really pushing to ON_QA now
This is likely a misconfiguration of the jmx props necessary to monitor tomcat 5/6. I have a Tomcat 5.5 instance being monitored right now. I am pretty sure (though not absolute) that this is in the automation suite too.
Closing as NOTABUG, we can reopen later if necessary.