Description of problem:
When EAP 6.x running in service/non-service mode on Linux, if use "kill -15 <EAP_PID>" or send TERM signal by system to shutdown EAP, there is no clear message in server.log to let user know the shutdown reason.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
For example, server.log is able to record that EAP was shutdown by signal TERM.
After that user can narrow down the issue quickly.
Please let us know if it is able to implement in next release?
What specific OS and JDK are being used? I believe in most cases the hotspot VM will honor shutdown hooks for SIGTERM. There is no guarantee that shutdown hooks will run though. There's likely not much we can do about this.
The description of problem states that there is no clear indication of shutdown reason, not just the fact that EAP 6 was shut down by request.
So, to re-iterate, what do we want in the logs in first place? Indication that server was shutdown by exactly SIGTERM signal or just "Server shutdown has been requested." as it is now in EAP7, as Brian mentioned?
> what do we want in the logs in first place?
Details on what triggered the shutdown.
Signal (and which signal), explicit shutdown command, System.exit() call, etc.
Note that in EAP 5 there are different logs for each of those triggers.
They're not explicitly stated (you have to know what logs correspond to what trigger), and the specific signal is not logged. But EAP 6 does not have any indication of what triggered a shutdown.
*** This bug has been marked as a duplicate of bug 1116086 ***