Details
-
Enhancement
-
Resolution: Obsolete
-
Major
-
7.3.2.redhat
Description
When restart of AMQ is requested as a notification from JBoss ON alert, this operation mostly works fine. However, sometimes, restart operation fails with the message:
******************************************************
java.lang.Exception: Restart failed while attempting to shut down: Was not able to stop the server
at org.rhq.core.pc.operation.OperationInvocation.run(OperationInvocation.java:278)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
*******************************************************
or
*******************************************************
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.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
*******************************************************
It seems that this issue is caused with "stop" operation.
When, for some reason, "soft" shutdown fails, AMQ server is left in a bad state. However this is still considered as UP in JBoss ON and attempt to execute start operation fails as one process is already running.
To resolve this, we should change the script so that "kill -9" is executed after unsuccessful "soft" shutdown.
Attachments
Issue Links
- is related to
-
-
- Closed
-
