-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using console-capture with StdErrLog results in empty log file #4620
Comments
Interesting ... |
Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
A minimal fix to Line 21 |
Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
Opened PR #4630 |
The minimal fix to So the behaviors of StdErrLog with regards to alternate PrintStream has been restored, allowing console-capture to do it's thing. |
Thanks Joakim, that did the trick... Prior to the quick fix there was warning message |
Issue #4620 - Better support for alt PrintStream in StdErrLog
Merged PR #4630 |
This fix didn't get merged to Jetty 10.0.x properly. |
+ The console-capture jetty module will reset System.err to RollingFileOutputStream. But that's too late, as StdErrAppender has already grabbed and is holding onto the System.err from earlier, which means it is not writing to the new System.err. Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>
…e-capture Issue #4620 - support alt PrintStream in StdErrAppender properly
The "jetty.console-capture.dir" was set and the server created the ...jetty.log file on launch, but the log messages were still being written to the console's Stderr and Stdout. As a workaround I replaced the
StdErrLog.class in the jetty-util-9.4.27.v20200227.jar with the version from jetty-util-9.4.26.v20200117.jar which restored the 9.4.26 behavior, writing the messages to the log file as per the 9.4.27 documentation.
The text was updated successfully, but these errors were encountered: