Details
-
Story
-
Resolution: Unresolved
-
Undefined
-
None
-
AMQ 7.11.0.GA
-
None
-
False
-
None
-
False
Description
There is some crucial JVM logging that always goes to standard out, and cannot be sent anywhere else. I'm thinking, in particular, of the TLS handshake debugging we get when running with `-Djavax.net.debug=ssl,handshake`; but not only that. Being unable to collect this logging makes troubleshooting TLS problems very difficult.
AMQ customers generally do not run their production brokers at a command line prompt, so the relatively simple expendient of `artemis run > my_log_file` is not open to them. Instead, they have to engage system administrators to reconfigure redirection at the service management level.
We need a way to capture standard out, and combine it with the main Artemis logging.