Bug 779139 (SOA-1537) - FILE apender configured with Threshold set to INFO in jboss-log4j.xml
Summary: FILE apender configured with Threshold set to INFO in jboss-log4j.xml
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1537
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Configuration
Version: 4.3 CP02
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: FUTURE
Assignee: trev
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-19 13:26 UTC by Matt Davis
Modified: 2011-12-05 19:29 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Linux x86
Last Closed: 2011-12-05 19:29:47 UTC
Type: Bug

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


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 777706 0 high CLOSED SOA-P production config - Out of the box log level definitions too verbose for a production environment (4K+ hibernate a... 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 778009 0 high CLOSED SOA Platform, standalone server, default configuration - log4j configuration = 300,000 log messages/hour on idle server 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker SOA-1537 0 None None None Never

Internal Links: 777706 778009

Description Matt Davis 2009-10-19 13:26:10 UTC 
Complexity: Low
Date of First Response: 2010-04-06 08:07:39
Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/353711
Workaround: Workaround Exists
Workaround Description: Comment out the following line in the FILE apender :
<param name="Threshold" value="INFO"/>
project_key: SOA

The jboss-log4j.xml file installs with the FILE appender configured with Threshold set to INFO.  This is problematic since the other jboss products ship without a Threshold for the file appender. Users have to go through the log4j configuration to figure out why their TRACE categories aren't being written to file.
Comment 1 trev 2009-10-19 14:23:25 UTC 
Link: Added: This issue is related to SOA-222
Comment 2 trev 2009-10-19 14:23:52 UTC 
Link: Added: This issue is related to SOA-536
Comment 3 Darran Lofthouse 2010-04-06 12:07:39 UTC 
In addition to the description here, if there is a desire to limit logging to INFO setting a Threshold on the appender would not cause log.isDebugEnabled() to return false meaning an logging optimisation would be skipped.
Comment 4 Rick Wagner 2011-12-05 19:29:47 UTC 
Release Notes Text: Added: Easily addressed by user, not worth the cost of converting and carrying this JIRA.  Closing.
Note You need to log in before you can comment on or make changes to this bug.