[
https://issues.jboss.org/browse/WFLY-7710?page=com.atlassian.jira.plugin....
]
Brian Stansberry commented on WFLY-7710:
----------------------------------------
Oops, I spoke too soon re: current console being better than EAP 6. It seems the current
console returns UI control to the user while the "stop" is proceeding in the
background. During this period, the UI presents the normal actions as if the server was
started. But once the "stop" operation aborts on the server side, the console
shows the action list as if the server was stopped.
I think this is a separate issue and may require some server side change to better report
to the console the real state of the server. But I think it's probably best to always
include the "Force Shutdown" option. Force Shutdown is primarily for
pathological situations and that means it's possible the HC is not clear on what the
state of the server is. So just always provide it as a choice.
Console does not provide an option to kill a server if normal
shutdown is hung
------------------------------------------------------------------------------
Key: WFLY-7710
URL:
https://issues.jboss.org/browse/WFLY-7710
Project: WildFly
Issue Type: Bug
Components: Web Console
Reporter: Brian Stansberry
Assignee: Harald Pehl
I'm experimenting with how an WildFly/EAP domain reacts to failure conditions and
noticed that the current console, if a server will not stop, will not provide an option to
kill the server.
My experiment involves a pathological app with a servlet that will never return from
it's deplpy() method, meaning the MSC service behind the servlet will never stop,
meaning a normal shutdown will never complete.
The EAP 6 console had "Stop" and "Force Shutdown" links for the
servers in the domain topology view. Current console has no "Force Shutdown".
EAP 6 console has it's own issues in this area, specifically that if the server
won't stop, the console reports it stopped anyway, and no longer provides the option
to stop or force shutdown. The current console is better in this regard; when the server
doesn't shut down the action selections for the server are still the same as if the
server was started. So it's just the kill/destroy that is missing.
See also related JIRA
https://issues.jboss.org/browse/WFCORE-2065 for how kill/destroy
are suboptimal on the server side. That's mostly an FYI in case during experiments
with this you find things are not behaving as you expect.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)