EAP5 - Enable Arjuna transactions logging

Environment

• Red Hat JBoss Enterprise Application Platform (EAP) 4
• Red Hat JBoss Enterprise Application Platform (EAP) 5
• Red Hat JBoss SOA Platform 5.3.1
• Red Hat JBoss SOA Platform 5.2

Issue

• How to Enable Transaction Logging in EAP-5

Resolution

Two actions are required:

1. Modify jboss-log4j.xml

<category name="com.arjuna">
        <priority value="TRACE"/>
</category>   

2. Modify jbossts-properties.xml (EAP 5) or jbossjta-properties.xml (EAP 4).

<!-- Logging enabled changing com.arjuna.common.util.logging.DebugLevel value from 0x00000000 to 0xffffffff -->
   <properties name="common">
        <!-- CLF 2.0 properties -->
        <property name="com.arjuna.common.util.logging.DebugLevel"
            type="System" value="0xffffffff"/>
        <property name="com.arjuna.common.util.logging.FacilityLevel"
            type="System" value="0xffffffff"/>
        <property name="com.arjuna.common.util.logging.VisibilityLevel"
            type="System" value="0xffffffff"/>
        <property name="com.arjuna.common.util.logger" type="System" value="log4j"/>
    </properties> 

Note that the jbossts-properties.xml modification will need a restart of the service. Once this is adjusted that actual capturing of the available arjuna logging can be modified via changes to jboss-log4j.xml.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.