Bug 724296 (BRMS-241)

Summary: Set a Threshold for the console appender in log4j.xml
Product: [JBoss] JBoss Enterprise BRMS Platform 5 Reporter: Tihomir Surdilovic <tsurdilo>
Component: unspecifiedAssignee: Tihomir Surdilovic <tsurdilo>
Status: CLOSED WONTFIX QA Contact:
Severity: unspecified Docs Contact:
Priority: high    
Version: 5.0.1   
Target Milestone: ---   
Target Release: 5.0.2   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/BRMS-241
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-04-06 20:37:12 UTC Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Deadline: 2010-03-12   

Description Tihomir Surdilovic 2009-11-04 16:43:02 UTC 
Date of First Response: 2009-11-04 12:16:21
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/361675
securitylevel_name: Public

By default all logs will be printed to the console. This creates a clutter of STDOUT messages of all severities. Please change the console appender to:

<appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender">
		<param name="Target" value="System.out"/>
		<param name="Threshold" value="FATAL"/>
		<layout class="org.apache.log4j.PatternLayout">
			<param name="ConversionPattern" value="%-5p %d{dd-MM HH:mm:ss,SSS} (%F:%M:%L) \t %m%n"/>
		</layout>
	</appender>

adding <param name="Threshold" value="FATAL"/> as the default setting.
Comment 1 Aaron Pestel 2009-11-04 17:16:21 UTC 
Main reason this is an issue is because users are required to deploy BRMS Manager on EAP, so when they deploy it out of the box and use it, they get a bunch of logs in the EAP console like this:

18:24:55,271 INFO  [STDOUT] DEBUG 03-11 18:24:55,271 (PackageItem.java:queryAssets:439) 	 QueryExec time is: 4
18:24:55,272 INFO  [STDOUT] DEBUG 03-11 18:24:55,272 (PackageItem.java:queryAssets:441) 	 org.apache.jackrabbit.core.query.lucene.QueryResultImpl$LazyScoreNodeIterator
18:24:55,273 INFO  [STDOUT] DEBUG 03-11 18:24:55,272 (PackageItem.java:queryAssets:433) 	 SQL is SELECT * FROM drools:assetNodeType WHERE jcr:path LIKE '/drools:repository/drools:package_area/mortgages/assets[%]/%' and drools:format='jar' AND drools:archive = 'false' ORDER BY drools:title
18:24:55,276 INFO  [STDOUT] DEBUG 03-11 18:24:55,276 (PackageItem.java:queryAssets:439) 	 QueryExec time is: 3
18:24:55,277 INFO  [STDOUT] DEBUG 03-11 18:24:55,277 (PackageItem.java:queryAssets:441) 	 org.apache.jackrabbit.core.query.lucene.QueryResultImpl$LazyScoreNodeIterator
Comment 2 Anne-Louise Tangring 2010-03-04 20:08:48 UTC 
Approved for 5.0.2 if done by due date.
Comment 3 Tihomir Surdilovic 2010-03-11 19:06:30 UTC 
After review, by setting the Threshhold to FATAL messages will be lost. Transferring to doc jira BRMS-262.
Comment 4 Tihomir Surdilovic 2010-03-11 19:06:56 UTC 
See BRMS-262
Comment 5 Len DiMaggio 2010-04-06 20:37:12 UTC 
Closing - the BRMS log4j.xml file was not changed - the problem was resolved in documentation in SOA-262.