Bugzilla – Full Text Bug Listing
| Summary: | Wrong usage of log level configuration because of StdErrLog | ||
|---|---|---|---|
| Product: | [RT] Jetty | Reporter: | MichZem <michael.zamir> |
| Component: | build | Assignee: | Athena Yao <athena> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | athena, jetty-inbox, michael.zamir |
| Version: | 7.0.0 | Keywords: | core |
| Target Milestone: | 7.0.1 M1 | ||
| Hardware: | PC | ||
| OS: | Windows Server 2003 | ||
| Whiteboard: | |||
The wrong code was seen in jetty 7.0.0 RC 6 I didnt look backward in the history r982 -- picked this up to get it out of the way. Thanks for the report, MichZem. |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US) AppleWebKit/532.0 (KHTML, like Gecko) Chrome/4.0.203.2 Safari/532.0 Build Identifier: When we want to increase the log level of jetty (as standalone, for ex), we should use the -D/myWebApps.DEBUG=true or simply -DDEBUG=true But the code, in StdErrLog (org.eclipse.jetty.util.log.StdErrLog.StdErrLog(String name)) is wrong: Instead of looking for -D.DEBUG=true, it looks for -Dnull.DEBUG=true The right code should be: this._name=name==null?"":name; _debug=Boolean.parseBoolean(System.getProperty(this._name+".DEBUG",Boolean.toString(__debug))); Reproducible: Always Steps to Reproduce: 1.Run jetty, by using java -D.DEBUG=true org.eclipse.jetty.start.Main 2.Jetty wont be verbosed: it still uses INFO as default level 3.Instead, use java -Dnull.DEBUG=true org.eclipse.jetty.start.Main and only then, jetty will be verbose.