Admin console shows incorrect server status in JBoss EAP 6
Issue
- When we gracefully shutdown the server instance, which means if server is already processing some client request then in that case it will wait for the client execution to complete.
- If a Server is not completely stopped, and if we try to start server instance using CLI command or from Admin console then we will get below exception
ERROR [org.jboss.as.controller.management-operation] (HttpManagementService-threads - 43) JBAS014612: Operation ("start-servers") failed - address: ([("server-group" => "main-server-group")]): java.lang.IllegalStateException
at org.jboss.as.host.controller.ManagedServer.start(ManagedServer.java:231)
at org.jboss.as.host.controller.ServerInventoryImpl.startServer(ServerInventoryImpl.java:188)
at org.jboss.as.host.controller.ServerInventoryImpl.startServer(ServerInventoryImpl.java:168)
. . . .
- If we can check server status using following CLI command, then it shows status as
STOPPING:
[domain@localhost:9999 /] /host=master/server-config=server2:read-attribute(name=status)
{
"outcome" => "success",
"result" => "STOPPING"
}
- Server is in
STOPPINGstatus but Admin console shows server isStopped.
Environment
- Red Hat JBoss Enterprise Application Platform (EAP)
- 6.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
