IT30159: Setting the "traceEnabled" configuration property to true on theMQ resource adapter does not enable trace

APAR status

• Closed as program error.

Error description

• When setting the "traceEnabled" MQ resource adapter
  configuration property in the JBoss application server
  "standalone.xml" file, as follows:
  
      <subsystem xmlns="urn:jboss:domain:resource-adapters:5.0">
          <resource-adapters>
              <resource-adapter id="wmq.jmsra.rar"
  statistics-enabled="true">
                  <archive>
                      wmq.jmsra.rar
                  </archive>
                  <config-property name="logWriterEnabled">
                      true
                  </config-property>
                  <config-property name="traceEnabled">
                      true
                  </config-property>
                  <config-property name="traceLevel">
                      10
                  </config-property>
              </resource-adapter>
          </resource-adapters>
      </subsystem>
  
  trace is not generated, even though MQ activity is taking place
  within the application server.
  

Local fix

• Enable MQ resource adapter trace using Java system properties.
  
  Two options are available.
  
  Option 1:
  ----------
  Set the traceEnabled=true and traceLevel=10 MQ resource adapter
  properties as Java system properties.
  
  Option 2:
  ----------
  Set the MQ common services tracing properties, as described in
  IBM Knowledge Center:
  
  https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_9.1.0/com.
  ibm.mq.tro.doc/q131840_.htm
  
  For example, set the property:
  
     "com.ibm.msg.client.commonservices.trace.status"
  
  to the value "ON" and the property:
  
    "com.ibm.msg.client.commonservices.trace.level"
  
  to the value="10".
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects users of JEE application servers that utilise
  the MQ resource adapter who need to collect MQ trace.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  After setting the "traceEnabled" MQ resource adapter
  configuration property to the value "true", trace was not
  enabled despite the property being correctly set by the JEE
  application server on the MQ resource adapter instance.
  

Problem conclusion

• The MQ resource adapter has been updated to ensure trace is
  enabled when the traceEnabled property is set to the value
  "true" in an application server's configuration.
  
  When collecting trace, it is advisable to also configure the
  output file location and name for trace by using the MQ common
  services property name:
  
     "com.ibm.msg.client.commonservices.trace.outputName"
  
  set as a Java system property.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v8.0       8.0.0.14
  v9.0 LTS   9.0.0.8
  v9.1 CD    9.1.4
  v9.1 LTS   9.1.0.4
  
  The latest available maintenance can be obtained from
  'WebSphere MQ Recommended Fixes'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
  
  If the maintenance level is not yet available information on
  its planned availability can be found in 'WebSphere MQ
  Planned Maintenance Release Dates'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
  ---------------------------------------------------------------
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  IBM MQ BASE MP

• Fixed component ID

  5724H7251

Applicable component levels