| Summary: | System.err messages coming out of the log from Tomcat during startup, installing bundles and shutdown | ||
|---|---|---|---|
| Product: | [RT] Virgo | Reporter: | Chris Frost <eclipse> |
| Component: | runtime | Assignee: | Glyn Normington <glyn.normington> |
| Status: | CLOSED NOT_ECLIPSE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | glyn.normington, milesg78 |
| Version: | 3.0.0.M06 | ||
| Target Milestone: | 3.0.0.RC1 | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
|
Description
Chris Frost
See also bug 351533 which the fix to this bug may help. I checked the behaviour of Virgo 2.1.0.RELEASE and this also includes corresponding log entries such as:
[2011-07-19 16:11:17.745] system-artifacts System.err
INFO: The APR based Apache Tomcat
Native library which allows optimal performance in production environments was
not found on the java.library.path:
.:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java
So closing this bug as working as designed. I will however check with a Tomcat expert to make sure Tomcat really is intending to write to System.err.
The Tomcat behaviour is actually a behaviour of the JUL ConsoleHandler ([1]) which directs all log records to System.err, regardless of their level. [1] http://download.oracle.com/javase/6/docs/api/java/util/logging/ConsoleHandler.html |