Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 685114

Summary:	Production profile Log4J configuration should use AsyncAppender for Cluster logging.
Product:	[JBoss] JBoss Enterprise Application Platform 5	Reporter:	Duncan Doyle <ddoyle>
Component:	jbossas	Assignee:	Fernando Nasser <fnasser>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	5.1.0
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-02-10 03:13:39 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.

Comment 1 Red Hat Bugzilla 2025-02-10 03:13:39 UTC

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.