1) Install EWS
2) Install Tomcats as services, start one of them
3) RHQ agent -> discovery -f - says Tomcat was found
4) Check RHQ web - not displayed. It's not ignored. Httpd or IIS were discovered.
Tomcat.Tomcat Server: Starting discovery...
Tomcat.Tomcat Server: Process scan detected a server - scan=[ProcessScan: query=[process|basename|match=^tomcat(5|6)\.exe], name=[WindowsEWSTomcat]], process=[p
rocess: pid=, name=[C:\Program Files\Red Hat\Enterprise Web Server\sbin\tomcat5.exe], ppid=]
Tomcat.Tomcat Server: Done.
This is similar to bug 580931 but still reproducible w/ RHQ 4.3.0-SNAPSHOT and EWS 1.0.2 installed on Win XP.
Author: Lukas Krejci <email@example.com>
Date: Fri Nov 18 12:43:46 2011 +0100
[BZ 688800] - More robust detection of EWS tomcat installation dirs.
commit 8088a9788c62d903630182a8038f6ec1b849d603 is in the master branch only.
To test this, please make sure that both tomcat 5 and 6 are discovered when started as Windows services and that the RHQ resource is fully functional when inventoried (configuration works, operations can be executed, etc.)
Code-reviewed the change committed to master. The change is good, no updates necessary.
Tomcat 5/6 is successfully detected by agent, appear in Discovery queue and
can be inventoried. Invoking operations work, however there is a new bug
Pushing to ON_DEV so change can be cherry-picked to release
git commit to release_jon3.x branch: f3ba0a0
changing status of VERIFIED BZs for JON 2.4.2 and JON 3.0 to CLOSED/CURRENTRELEASE