Bug 779364 (SOA-1754)

Summary: Documentation task - we should highlight the logging configuration change referenced in SOA-1553
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Len DiMaggio <ldimaggi>
Component: Documentation, CompatibilityAssignee: David Le Sage <dlesage>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.0.0 ER5   
Target Milestone: ---   
Target Release: 5.0.0 GA   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1754
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-02-15 19:09:43 UTC Type: Task
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Len DiMaggio 2009-12-22 14:38:45 UTC 
Date of First Response: 2010-02-11 22:41:01
project_key: SOA

See:
   https://jira.jboss.org/jira/browse/SOA-1553?focusedCommentId=12501079#action_12501079

We hit this problem in performance testing - users who have customized their logging may also hit the same problem.
Comment 1 David Le Sage 2010-02-12 03:41:01 UTC 
I have added this draft text to the "Migration" section of the Release Notes:


Potential Performance Issues Related to Logging

    If you have a customized logging definition, it may not pick up changes made in the new release,
    which can lead to a performance issue. The log level is set in bin/run.conf:

    JAVA_OPTS="-Xms256m -Xmx728m -XX:PermSize=256m -XX:MaxPermSize=512m
    -Djava.awt.headless=true -Djboss.server.log.threshold=INFO
    -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000
    -Dsun.rmi.dgc.server.gcInterval=3600000
    -Dsun.lang.ClassLoader.allowArraySyntax=true"


   It also needs to be set in the server's jboss-log4j.xml file:

            <priority value="${jboss.server.log.threshold}"/>
            <appender-ref ref="CONSOLE"/>
            <appender-ref ref="FILE"/>

   It is this latter change that can be missed if you have a customized configuration. To avoid this
   problem, do not reuse old customized logging defintions.
Comment 2 Len DiMaggio 2010-02-15 19:09:43 UTC 
Verified in the docs here:
  http://documentation-stage.bne.redhat.com/docs/en-US/JBoss_Enterprise_SOA_Platform/5.0.0/html-single/Release_Notes/#sect-migrating