Hide Forgot
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.
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.
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