DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19906>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19906

[ENH] Further logging improvements





------- Additional Comments From [EMAIL PROTECTED]  2003-07-23 19:40 -------
Some observations after applying the patches:

1. We may want to remove the classname for the format pattern - it makes the 
log entry hard to read.
2. How do we activate logging for the PortletStats service (access.log)?
3. There are still logging properties in tr.props? I assume that they are not 
used. If so, we should take them out and deprecate Turbine logging completely.
4. Get these in stdout on startup:

log4j:WARN No appenders could be found for logger 
(org.apache.jetspeed.services.logging.JetspeedLoggingService).
log4j:WARN Please initialize the log4j system properly.
1062 [Thread-16] INFO component.ComponentLoader  - loading component: 
name=fulcrum class=org.apache.fulcrum.Fulcrum config=C:\jakart
a-tomcat-3.3.1a\webapps\jetspeed\WEB-INF\conf\Fulcrum.properties
1182 [Thread-16] INFO fulcrum.TurbineServices  - Finished initializing all 
services!
1182 [Thread-16] INFO logging.JetspeedLoggingService  - Finish Initializing 
service (early): ComponentService
1182 [Thread-16] INFO logging.JetspeedLoggingService  - Start Initializing 
service (early): JetspeedLogFactoryService

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to