Bug 865454

Summary:	Cannot manage tomcat7's deployed web applications
Product:	[JBoss] JBoss Enterprise Web Server 2	Reporter:	Jan Martiska <jmartisk>
Component:	JON Plugin	Assignee:	Jean-frederic Clere <jclere>
Status:	CLOSED DUPLICATE	QA Contact:	Mike Foley <mfoley>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	ccrouch, jdoyle, lfuka, loleary, mfoley, mhusnain, myarboro
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: ?? Consequence: For the ZIP version of JBoss Enterprise Web Server, all deployed web applications unexpectedly appear "unavailable" and management operations applies to them are ineffective. As an example, a stop operation on a running web application results in the following error: Fix: None Result: None Workaround: None	Story Points:	---
Clone Of:
Clones:	921261 (view as bug list)		Environment:
Last Closed:	2013-04-12 16:06:56 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:

Description Jan Martiska 2012-10-11 13:29:14 UTC

Tomcat7 version: JBoss EWS 2.0.0.CR1 (installed from ZIP)
All deployed webapps appear as 'unavailable'. And it looks like no management operations on them work. For example invoking a 'stop' operation on a running webapp will end with:

java.lang.IllegalStateException: Could not find MBean for WAR '//localhost/my-simple-webapp'.
	at org.jboss.on.plugins.tomcat.TomcatWarComponent.invokeOperation(TomcatWarComponent.java:350)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:616)
	at org.rhq.core.pc.inventory.ResourceContainer$ComponentInvocationThread.call(ResourceContainer.java:634)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
	at java.lang.Thread.run(Thread.java:679)

By the way, deploying new applications works fine, but you cannot manage them after that anymore.

Comment 1 mark yarborough 2012-11-12 20:22:32 UTC

This bug needs a corresponding bug in Jira or Bz (as appropriate) owned by the plugin team. Mark Yarborough work with John Doyle to define EWS owner.

Comment 2 Rémy Maucherat 2012-12-14 16:31:57 UTC

Both work for me now, and were likely caused by bad mbean names. The mbean names got fixed by the Tomcat 7 support patch. If there is a problem, a new bug should be filed using a build that uses the RHQ version that has acked support for Tomcat 7.

Comment 3 Libor Fuka 2013-01-18 12:43:55 UTC

Do we have this patch in EWS 2.0.0.GA ?
I think no.

Comment 4 Larry O'Leary 2013-03-13 19:28:56 UTC

Web applications are shows as unavailable due to the stateName value being returned as "STARTED" when for whatever reason, we are expecting "1".

Comment 6 Larry O'Leary 2013-04-12 16:06:56 UTC

Closing this as it duplicates the already cloned bug that had been captured in EWS.

*** This bug has been marked as a duplicate of bug 921261 ***