Hide Forgot
Description of problem: The discovery process for Tomcat 6 fails and the resource is always down. How reproducible: Every time. Steps to Reproduce: 1. Start a Tomcat 6 instance (used 6.0.32) 2. Attempt to inventory it. 3. Observe results Actual results: None of the server child resources are discovered and Tomcat 6 is always down. Expected results: The inventory process works like Tomcat 5 and all the children (eg. webapps) are inventoried. Additional info: The following error message is displayed in the logs: 2011-11-30 17:56:15,146 INFO [ResourceContainer.invoker.daemon-40] (org.mc4j.ems.connection.ConnectionFactory)- Connection library dependancy [catalina-cluster.jar] not found in directory: /home/snegrea/Downloads/jboss-ews-1.0/tomcat6 2011-11-30 17:56:15,150 INFO [ResourceContainer.invoker.daemon-40] (org.mc4j.ems.connection.ConnectionFactory)- Connection library dependancy [catalina-optional.jar] not found in directory: /home/snegrea/Downloads/jboss-ews-1.0/tomcat6 Since those two libraries are Tomcat 5 specific most probably the Tomcat plugin confuses Tomcat 6 with Tomcat 5. I found no other error messages in the logs related to this failure. The JMX settings have been set correctly in startup.sh prior to starting Tomcat 6.
I tested this with JON CR3 and only EWS plugin installed. The agent was started without the EWS plugin installed and used "plugins update" to get the tomcat plugin after server installation. The reported error persisted until I restarted the agent. The discovery process worked correctly for Tomcat 6 after agent restart.
QE ... please verify that we can inventory Tomcat6 ...
was able to inventory both tomcat5 and tomcat6. both installed, only tomcat6 running. attaching agent log as evidence.
Created attachment 547338 [details] agent log
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE