Bug 580931

Summary:	EWS 1.0.1 not detected (Windows?)
Product:	[Other] RHQ Project	Reporter:	Corey Welton <cwelton>
Component:	Plugins	Assignee:	John Sanda <jsanda>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Satish Mohan <smohan>
Severity:	high	Docs Contact:
Priority:	high
Version:	1.4	CC:	smohan
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Windows
Whiteboard:
Fixed In Version:	2.4	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-08-12 16:59:23 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	577051

Description Corey Welton 2010-04-09 14:13:40 UTC

Description of problem:
JON cannot detect an install of EWS 1.0.1

Version-Release number of selected component (if applicable):


How reproducible:
Every time


Steps to Reproduce:
1.  Install JON server; assure EWS plugin is installed.  
2.  Install agent on this platform, and wait for inventory to be populated.
3.  Install EWS 1.0.1 on said platform; wait for resource to be discovered and/or run manual autodiscovery.
 
Actual results:
EWS is not detected

Expected results:
EWS can be detected and monitored.

Additional info:
This test was performed on a Windows system; it is currently unknown whether this is platform-specific or cross-platform.  Tests will continue on other platforms.

Comment 1 Corey Welton 2010-04-09 15:40:23 UTC

Installed EWS 1.0.1 on Linux; it was detected appropriately.

Comment 3 John Sanda 2010-04-13 20:27:46 UTC

I have an EWS 1.0.1 Tomcat6 server running on a Windows 2003 box and on a Fedora 12 box. The one running on the Fedora 12 box was discovered but not the one running on the Windows 2003 box.

Comment 4 John Sanda 2010-04-13 20:46:37 UTC

Corey,

On what version of Windows did you test?

Comment 5 John Sanda 2010-04-14 17:04:09 UTC

Initially I was starting the tomcat server using EWS_HOME/sbin/tomcat6.exe and the process during discovery was not finding it. Then I discovered EWS_HOME/share/apache-tomcat-6.0.24 which appears to be a normal tomcat install directory. When I start tomcat using EWS_HOME/share/apache-tomcat-6.0.24/bin/startup.bat the tomcat server gets discovered.

I also added the jmx system properties described at http://www.rhq-project.org/display/JOPR2/Best+Practices+for+Managing+Tomcat+Servers so that I was able to connect to the server and collect metrics and what not.

I do not know what the tomcat6.exe and other files in EWS_HOME/sbin are for, but I am going to open a separate bug for some improved documentation. I will link this bug to it.

Corey, I am marking this as ON_QA so that you can verify for yourself.

Comment 6 John Sanda 2010-04-15 18:51:49 UTC

Discovery failed when I tried running tomcat as a service. And that is because the service uses the tomcat6.exe to start tomcat.

Comment 7 Corey Welton 2010-04-19 13:19:44 UTC

Moving back to dev while the tomcat6.exe issue is being resolved.

Comment 8 John Sanda 2010-04-19 13:30:12 UTC

I am working on updating the tomcat plugin so that it is compatible with the tomcat5.exe and tomcat6.exe executables. The work will be tracked against this bug.

Comment 9 Corey Welton 2010-04-20 01:45:20 UTC

FWIW, i just launched tomcat as a service, a la:

'call service6.bat install'


I watched it start up, waited a while, did a manual autodiscovery against the agent.... never see any tomcat instances show up in inventory for this system.

Color me skeptical that we're seeing this work reliably and/or as expected.

Comment 10 John Sanda 2010-04-21 13:52:32 UTC

Running the command,

call service6.bat install

does not actually start tomcat. It only configures it so that it can be run as service. You still need to start the service. From the Start menu go to Start --> All Programs --> Administrative Tools --> Services. Look for and click on Apache Tomcat 6. You can then start tomcat by clicking on the 'Start' link on the left.

Comment 11 John Sanda 2010-04-21 14:13:19 UTC

Thought the following comment got added yesterday but never made it:

The change needed to get discovery working EWS on Windows is being able to
determine catalina.home, which is the base directory of the tomcat
installation. Once the plugin determines it, it can resolve everything else
relative to that location.

I just pushed 7dce7107f556e4a3b473a55275da8148194eb37c to the bugfixes branch.
The commit includes a couple changes to the tomcat plugin. First, I added a new
process-scan query to detect tomcat5.exe and tomcat6.exe. Secondly, if
catalina.home cannot be determined from the command line arguments and we are
running on windows, the plugin basically checks to see if we are running out of
an EWS installation directory structure and resolves catalina.home relative to
the EWS directory structure.

I have tested this on Windows against both with the tomcat 5 and tomcat 6
packages that are included with EWS.

Comment 12 John Sanda 2010-04-22 21:26:39 UTC

Changes merged into master. Moving to ON_QA.

Comment 13 Corey Welton 2010-05-03 20:33:36 UTC

QA verified.

Comment 15 Corey Welton 2010-08-12 16:59:23 UTC

Mass-closure of verified bugs against JON.