Description of problem:
When EAP 6 is shutdown, there is no logging indicating what triggered the shutdown.
This is a problem when the shutdown is not expected, as there are no clues
to help debug what caused EAP to shutdown.
In EAP 5 different shutdown triggers caused different logging:
We need the equivalent (or better) in EAP 6 to debug these cases.
Cases that need to be covered:
- OS signal (preferably with which signal it is)
- Explicit shutdown (preferably with the source -- CLI, admin console, etc. and the account)
This may already be available with audit logging? But should always be logged even if audit logging is not enabled.
Note that AFAIK there was no special handling in EAP < 6 for System.exit(), beyond the lack of logs. I don't expect there would be in EAP 6 either. Logging when the shutdown handler is invoked or when a management op requests shutdown is more feasible.
Details about who invoked the management op or the interface they came in from are provided via audit logging. I don't expect we'll provide them otherwise as that would involve exposing sensitive information to types of code that otherwise wouldn't/shouldn't have access. If that proves not to be the case we'll consider it.
In domain mode, the PC logs will also give you some information for signals. High exit codes indicate a signal of id n-128 or n-127 (I can't remember which off the top of my head).
Closed as it is an RFE, opened RFE for EAP 7 consideration
PR sent https://github.com/jbossas/jboss-eap/pull/2839 that consists backports of both WFCORE-1498 and WFCORE-1686 and supersedes the older Fedor's PR https://github.com/jbossas/jboss-eap/pull/2776
Verified with EAP 6.4.11.CP.CR1
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.
*** Bug 1328673 has been marked as a duplicate of this bug. ***