[jboss-jira] [JBoss JIRA] Closed: (JBAS-5274) Default log4j conversion pattern should log Thread name
[ http://jira.jboss.com/jira/browse/JBAS-5274?page=all ]
Dimitris Andreadis closed JBAS-5274.
------------------------------------
Resolution: Done
Assignee: Dimitris Andreadis (was: Galder Zamarreno)
Galder, I've made the change:
<!-- The default pattern: Date Priority [Category] (Thread) Message\n -->
<param name="ConversionPattern" value="%d %-5p [%c] (%t)
%m%n"/>
A simple start/shutdown of the default config, gives a server.log that is 3% percent
bigger, and the start-up time looks like rougly a second slower (+3%) so that's not
too bad, I guess.
Let's leave it changed to measure people's reaction.
Default log4j conversion pattern should log Thread name
-------------------------------------------------------
Key: JBAS-5274
URL: http://jira.jboss.com/jira/browse/JBAS-5274
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Logging
Reporter: Galder Zamarreno
Assigned To: Dimitris Andreadis
Fix For: JBossAS-5.0.0.CR1
From a support point of view, I often find myself asking users/customers to enable the
full conversion pattern in the server.log's log4j appender in order to get a better
idea of
what each thread is doing.
I suggest that we add %t to the default conversion pattern to to speed up problem
resolution.
The server.log is already verbose enough and few of our users/customers understand it, so
I wouldn't expect such change to have a major impact on our users/customers:
<!-- The default pattern: Date Priority [Category] (Thread) Message\n -->
<param name="ConversionPattern" value="%d %-5p [%c] (%t)
%m%n"/>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira