Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 950448

Summary:	java.lang.Exception thrown when take 20~30 sec to start EAP
Product:	[JBoss] JBoss Operations Network	Reporter:	Hisanobu Okuda <hokuda>
Component:	Operations	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Mike Foley <mfoley>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	JON 3.1.2	CC:	loleary, myarboro, tsegismo
Target Milestone:	---
Target Release:	JON 3.2.0
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-07-04 08:53:48 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 Hisanobu Okuda 2013-04-10 09:08:52 UTC

Description of problem:
java.lang.Exception thrown when take 20~30 sec to start EAP.

java.lang.Exception: Was not able to start the server
	at org.rhq.core.pc.operation.OperationInvocation.run(OperationInvocation.java:278)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)

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


How reproducible:


Steps to Reproduce:
1. register EAP on JON
2. add :-
JAVA_OPTS="$JAVA_OPTS -Xrunjdwp:transport=dt_socket,address=8787,server=y,suspend=y"
in standalone.conf
3. start EAP on JON
4. the exception thrown
5. attach a debugger to EAP process then run

step 2 and 5 simulates that EAP take a long time (>20 sec) to start up.

Actual results:


Expected results:


Additional info:

Comment 1 Charles Crouch 2013-04-12 15:28:41 UTC

This appears to be working as designed, the EAP server didnt start and we should have failed the operation. In 3.2, at least, there is an option to specify a timeout for the operation so that it waits longer before failing.

Comment 2 Larry O'Leary 2013-04-18 21:16:07 UTC

Yes. I can confirm. The steps described only demonstrate that the plug-in and operation are working as designed. However, perhaps the error should indicate something more appropriate?

> The start operation may have failed as the resource did not become available within <timeout> seconds. Wait a while and check the resource's availability to confirm.

Comment 3 Thomas Segismont 2013-06-17 15:42:02 UTC

This looks like a duplicate of BZ966777

Comment 4 Thomas Segismont 2013-07-04 08:53:48 UTC


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