Bugzilla – Full Text Bug Listing
| Summary: | Jetty prints unwanted messages to System.out | ||
|---|---|---|---|
| Product: | [RT] Jetty | Reporter: | Rüdiger Herrmann <ruediger.herrmann> |
| Component: | server | Assignee: | Greg Wilkins <gregw> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | janb, jetty-inbox, joakim.erdfelt |
| Version: | 8.0.1 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
I am using Jetty 8.0.2.SNAPSHOT from 2011-10-04 What logging framework are you using? Internal StdErrLog Slf4J? Java.util.logging? (In reply to comment #2) > What logging framework are you using? > [ ... ] I use a custom implementation of org.eclipse.jetty.util.log.Logger. I found out that it is a debug message that is passed to the logger which then prints to System.out. Is it inteded that code from AsyncHttpConnection actively enables debug messages (method handle, line 141)? The NO_PROGRESS detection was intended to enable debugging. But we believe that we have now found the cause of that NO_PROGESS problem so the handling no longer enables debugging on NO PROGRESS.
However it will still log a warning and a dump - which if you see, you should raise and issue.
Also the the "handle {}" should have been expanded, but is obviously not being done by you custom org.eclipse.jetty.util.log.Logger. You may want to borrow the code from StdErrLog#format(StringBuilder builder, String msg, Object... args) to expand the {} in the strings.
Can you confirm that you are not seeing such debug in the 8.0.2 release?
Thanks for your thorough explanation (In reply to comment #4) > The NO_PROGRESS detection was intended to enable debugging. But we believe that > we have now found the cause of that NO_PROGESS problem so the handling no longer > enables debugging on NO PROGRESS. > > However it will still log a warning and a dump - which if you see, you should > raise and issue. I will do if I see such a warning > Also the the "handle {}" should have been expanded, but is obviously not being > done by you custom org.eclipse.jetty.util.log.Logger. You may want to borrow > the code from StdErrLog#format(StringBuilder builder, String msg, Object... > args) to expand the {} in the strings. Yes, the {} are caused by my poor logger implementation > Can you confirm that you are not seeing such debug in the 8.0.2 release? The http://download.eclipse.org/jetty/updates/jetty-bundles-8.x repo still shows 8.0.1 Where can I find a p2 repo/bundles of the 8.0.2 release? Rüdiger, The 8.0.2 bundles were there, just not listed on the index page. They are now: http://download.eclipse.org/jetty/updates/jetty-bundles-8.x/ cheers Jan (In reply to comment #6) > The 8.0.2 bundles were there, just not listed on the index page. They are now: > http://download.eclipse.org/jetty/updates/jetty-bundles-8.x/ > > Jan Thanks Jan, from my POV the issue can be closed. I would reopen if the warning reappears. Fixed for 8.0.2 |
When an (application) exception occurs, Jetty prints the exception stack trace and floods the console with handle/unhandle messages : handle {} unhandle {} handle {} unhandle {} ...