Even though you set "org.collaxa.thirdparty.jgroups” logging level from BPELConsole to minimum, still you will find that jgroup messages are logged in file. To have full control on JGroups logging, please perform the following steps:
- Stop the OC4J process using opmnctl
- Open the $ORACLE_HOME/j2ee/<oc4j_name>/config/j2ee-logging.xml file and add the following log handler for jgroups. You can change the path to any other directory. I have set it to $ORACLE_HOME/bpel/system/logs/jgroups folder where a log.xml will be created. This file will contain the jgroups log messages:
<log_handler name="jgroups-handler" class="oracle.core.ojdl.logging.ODLHandlerFactory">
<property name="path" value="%ORACLE_HOME%/bpel/system/logs/jgroups"/>
<property name="maxFileSize" value="10485760"/>
<property name="maxLogSize" value="104857600"/>
<property name="encoding" value="UTF-8"/>
<property name="supplementalAttributes" value="J2EE_APP.name,J2EE_MODULE.name"/>
</log_handler>
Add the following logger, immediately below the org.quartz logger:
<logger name="org.collaxa.thirdparty.jgroups" level="SEVERE" useParentHandlers="false">
<handler name="jgroups-handler"/>
</logger>
- Start the BPEL OC4J process using opmnctl and confirm the jgroups trace level messages in the $ORACLE_HOME/bpel/system/logs/jgroups/log.xml file.
- You can use the EM console to change the level for "org.collaxa.thirdparty.jgroups" to the desired level, or directly edit this file and change the level.
