Bug 921194

Summary:	[tomcat] Connectors are not properly discovered and therefore are unavailable along with all their content
Product:	[JBoss] JBoss Enterprise Web Server 2	Reporter:	Larry O'Leary <loleary>
Component:	JON Plugin	Assignee:	Jean-frederic Clere <jclere>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavel Slavicek <pslavice>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	2.0.0	CC:	atangrin, ccrouch, jawilson, jdoyle, jmartisk, lfuka, majoshi, mfoley, mhasko, mhusnain, myarboro
Target Milestone:	---
Target Release:	2.0.1
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Due to an issue in the JBoss Enterprise Web Server plug in, the connectors <literal>?-8080</literal> and <literal>?-8009</literal> are down. As a result, Tomcat 7 can not be monitored or managed. The bug in the JBoss Enterprise Web Server plug in is now fixed. As a result, the connectors are now discoverable and are named <literal>http-bio-8080</literal> and <literal>ajp-bio-8009</literal> as expected and Tomcat 7 can be managed and monitored successfully.	Story Points:	---
Clone Of:	921191	Environment:
Last Closed:	2014-01-03 12:58:35 UTC	Type:	Bug
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:	707349
Bug Blocks:	956987, 956990

Description Larry O'Leary 2013-03-13 16:45:08 UTC

+++ This bug was initially created as a clone of JBoss ON Bug #921191 +++

Description of problem:
Tomcat 7 can not be monitored/managed due to the connectors failing to be properly discovered and configured.

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

How reproducible:
Always

Steps to Reproduce:
1.  Configure Tomcat 7 from EWS 2.0 for management from JBoss ON
2.  Start Tomcat 7 from EWS 2.0.
3.  Start JON 3.1.2.
4.  Import Tomcat 7 instance into JON inventory.
  
Actual results:
Connectors are DOWN and their names are ?-8080 and ?-8009. 

Expected results:
Connectors should be up and have the names http-bio-8080 and ajp-bio-8009.

Comment 6 Larry O'Leary 2013-04-12 17:36:49 UTC

*** Bug 865488 has been marked as a duplicate of this bug. ***

Comment 7 Libor Fuka 2013-05-10 12:53:59 UTC

Verified with Tomcat plugin brew build [1] and EWS 2.0.1.ER1 Tomcat7, Tomcat6 and EWS 1.0.2 GA T5, T6 - RHEL, Windows, Solaris
[1] https://brewweb.devel.redhat.com//buildinfo?buildID=269954

Some new bugs found 961253 (EWS 1.0.2 Tomcat5 - possible Tomcat 5 bug) and 
AJP Tomcat connector name is displayed ajp-xxx in RHEL, MS Windows and Solaris Intel, but on Solaris SPARC the name is displayed like jk-xxxx in JON UI.
It should be the same for all platforms.

Comment 8 Mandar Joshi 2013-05-14 06:25:44 UTC

Added DocText.

@Wei Nan Li, can you please review the Doc Text content?

Comment 9 Mandar Joshi 2013-05-14 06:49:24 UTC

oops..

@Jean-Frederic Clere,  can you please review the Doc Text content?

Comment 10 Jean-frederic Clere 2013-05-14 08:34:23 UTC

"Cause: Tomcat 7 can not be monitored/managed due to the connectors failing to be properly discovered and configured.

Consequence: Connectors are DOWN and their names are ?-8080 and ?-8009

Fix: The bug in the JBoss Enterprise Web Server plugin has now been fixed.

Result: The connectors are now up and have the names http-bio-8080 and ajp-bio-8009. Tomcat 7 can now be monitored/managed successfully."

Looks Ok.

Comment 11 Libor Fuka 2013-05-15 10:21:29 UTC

I reviewed again all Solaris SPARC and Intel JON plugin test runs and here are the results:
EWS 2.0.1 ER1 T6, T7 on Solaris Intel(32 and 64 bits) and on Solaris SPARC - connector names in JON UI are correct ajp-, http-

EWS 1.0.2 GA T5, T6 on Solaris Intel(32 and 64 bits) - connector names in JON UI are correct ajp-, http-
EWS 1.0.2 GA T5, T6 on Solaris SPARC - connector name has jk- instead of ajp-

Comment 12 Libor Fuka 2013-05-15 11:10:24 UTC

It was typo bug in test automation.
This bug is verified.