Hide Forgot
Date of First Response: 2010-03-11 14:12:40 Help Desk Ticket Reference: https://enterprise.redhat.com/issue-tracker/361675 securitylevel_name: Public This is from BRMS-241 The BRMS war includes it's own log4j.xml configuration file in $BRMS_WAR/WEB-INF/classes directory. This configuration defines a single console appender which prints to STDOUT: <appender name="CONSOLE" class="org.apache.log4j.ConsoleAppender"> <param name="Target" value="System.out"/> <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> The system log4j ($server/$configuration/conf/jboss-log4j.xml) then intercepts STDOUT and logs it to the console. In the user guide we should describe how users can redirect all STDOUT messages to the AS FILE appender (be written to the server logs) For this in $server/$configuration/conf/jboss-log4j.xml user can add a new category: <category name="STDOUT" additivity="false"> <priority value="INFO" /> <appender-ref ref="FILE"/> </category>
Summary for clarification: * The BRMS WAR has its own log config that directs all output to STDOUT * The default JBoss log config directs STDOUT to the console * This configuration change is to direct STDOUT to the server logs instead.
This doesn't occur when deployed on EAP 4.3.CP07 with the production profile. It does occur with the "default" profile.
Added to BRMS User Guide, created new Logging section with following content: The JBoss Enterprise BRMS Platform web application uses log4j for logging. The configuration included in the WAR, WEB-INF/classes/log4j.xml, sends all messages to STDOUT. When deployed on the JBoss Enterprise Application Platform where these messages are displayed depends on the server profile. When using the production profile, the log messages are appended to the server log file, $PROFILE/log/server.log. When deployed on the default server profile, the log messages are displayed on the server console. To change the logging behavior, edit the log4j configuration file for the server profile, jboss-as/server/$PROFILE/conf/jboss-log4j.xml Adding the following XML to the log4j configuration of the default server profile will create a new category that directs the STDOUT messages to server log file. <category name="STDOUT" additivity="false"> <priority value="INFO" /> <appender-ref ref="FILE"/> </category> Refer to the JBoss Enterprise Application Platform documentation for additional logging configuration information.
Is this content accurate and adequate ? Any suggestions ?
Darrin, this is really good. Thanks!
Content has been verified. I'm not really happy with the language in the "what happens in each profile" paragraph, I'll make a note to take another look at it before release if there is time.
Added to 5.0.2 release notes as a resolved issue: BRMS-262 A new section (2.7) has been added to the BRMS User Guide to provide some guidance on alternative logging configurations.