Bug 1400629

Description of problem:

The console only displays the 'Force Shutdown' link if it believes the server is started. But in some pathological situations, a broken server can fail to shut down when the 'Stop Server' link in clicked, but the DC and console don't communicate that effectively to each other, the console thinks the server is stopped, and no longer displays the 'Force Shutdown' link. The user is forced to use the CLI or OS tools to kill the server.

Since 'Force Shutdown' is used to deal with pathological conditions, the simply solution is to always provide the 'Force Shutdown' link.

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

6.4 CP11

How reproducible:

Always

Steps to Reproduce:
1. Deploy an application to a server group that includes logic that will not let MSC stop a service. I'll attach such an app in a moment; it includes a servlet destroy() method that will never return, resulting in the service used for that servlet never stopping.
2. For one of the servers that has the app deployed, click the 'Stop Server' link.

Actual results:

Server cannot completely stop normally and needs to be killed. But the console reports it as stopped and does not display the 'Force Shutdown' link.

Expected results:

Server cannot completely stop normally and needs to be killed. The console reports it as stopped but continues to display the 'Force Shutdown' link, giving the user the option to kill the server.


Additional info:

I consider improving the server state communication between the domain and the console such that the console doesn't regard the server as stopped as being out of scope here. It's a valid thing to look at upstream, but what I propose here is a simple fail safe.