Description of problem: I was working on bug 580931 which involved a tomcat server from an EWS installation running on windows not getting discovered. The problem turned out to be that I was using the wrong start up executable. I first found several executables under EWS_HOME/sbin. I tried using EWS_HOME/sbin/tomcat6.exe and my server did not get discovered. But when I used EWS_HOME/share/apache-tomcat-6.0.24/bin/startup.bat it got discovered as expected. I think we need some better documentation around managing EWS on a Windows box. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Looking at http://www.redhat.com/docs/en-US/JBoss_Enterprise_Web_Server/1.0.1/html-single/Release_Notes/index.html#Install_On_MS_Windows I don't see any information on how to run Tomcat EWS as anything other than a service?
Rajesh, can you assign this to someone who can help us understand how Tomcat EWS should be started. Thanks Charles
The best person to answer these questions is the productization team who designed these scripts. Assigning to Permaine Cheung
Mladen, can you please provide some info on how Tomcat should be started on Windows? Thanks, Permaine
John, do you think we need to update our EWS discovery routines to be more robust, and find the running process when it is started different ways?
jsanda - do you recall any of the details/issues there might be in enhancing our ews detection
(In reply to comment #5) > John, do you think we need to update our EWS discovery routines to be more > robust, and find the running process when it is started different ways? If Tomcat is going to be started in ways that we have not accounted for as appears to be the case here, then yes, I absolutely think we want to ensure that our discovery routines are tested against all the supported ways of starting Tomcat.
Do the steps in bug 756098 cover the required setup here?