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:
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.
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.
This looks like a duplicate of BZ966777
*** This bug has been marked as a duplicate of bug 966777 ***