Bug 685114 - Production profile Log4J configuration should use AsyncAppender for Cluster logging.
Summary: Production profile Log4J configuration should use AsyncAppender for Cluster l...
Keywords:
Status: NEW
Alias: None
Product: JBoss Enterprise Application Platform 5
Classification: JBoss
Component: jbossas
Version: 5.1.0
Hardware: All
OS: All
unspecified
low
Target Milestone: ---
: ---
Assignee: Fernando Nasser
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-15 10:40 UTC by Duncan Doyle
Modified: 2011-04-08 22:55 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Duncan Doyle 2011-03-15 10:40:07 UTC 
Description of problem:
On production systems we advice to use the AsyncAppender for every Log4J appender. The default jboss-log4j.xml configuration in the EAP 'production' profile configures this appender for the FILE appender, which is used by the root logger. However, the default CLUSTER appender which is used to log cluster information (HA and JGroups) does not use an AsyncAppender.

Version-Release number of selected component (if applicable):
JBoss EAP 5.1

How reproducible:
Look at the $JBOSS_HOME/server/production/conf/jboss-log4j.xml file.
  
Actual results:
CLUSTER appender is used directly by the 'org.jboss.ha' and 'org.jgroups' categories.

Expected results:
CLUSTER appender should be wrapped in an ASYNC_CLUSTER appender which should be used by the 'org.jboss.ha' and 'org.jgroups' categories.
Note You need to log in before you can comment on or make changes to this bug.