IBM Support

IT39972: MQ Classes for Java/MQ JMS for Java with trace enabled can result in unexpected increased indentation for methods

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Running MQ Classes for Java/IBM MQ JMS for Java application with
    trace enable can result in unexpected increase in method
    indentation in the trace output.  This can result in the trace
    file containing large quantity of "-+:" character being repeated
    for method calls as the trace output is written.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of the MQ Classes for Java and IBM MQ
    classes for JMS using XA Transaction (JmqiXAResource) end and
    rollback methods with MQ Tracing enabled.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    With a MQ Classes for Java and IBM MQ classes for JMS using XA
    Transaction (JmqiXAResource) end and rollback methods with MQ
    Tracing enabled. The trace output can show an increasing indent
    of the method in the trace output.  This happens if the
    application obtains the MQ Session XAResource and performs the
    end and rollback method calls on the XAResource that result in
    an Exception being generated by the Method.  If the application
    repeats these method call over time the trace output increase
    the indentation of the method calls.
    
    The trace looks like:
    
    [16/02/22 12:28:54.858.00]  00000001  @2def8a7d
    c.i.mq.jmqi.JmqiXAResource
             {  end(Xid,int) [format: 1, gtrid: 6170706C65, bqual:
    62616E616E61] [536870912(0x20000000)]
    ...
    [16/02/22 12:28:54.873.03]  00000001  @2def8a7d
    c.i.mq.jmqi.JmqiXAResource
           -  !  end(Xid,int), The method 'xa_end' has failed with
    errorCode '100'. [javax.transaction.xa.XAException]
    [16/02/22 12:28:54.874.00]  00000001  @2def8a7d
    c.i.mq.jmqi.JmqiXAResource
           -  {  rollback(Xid) [format: 1, gtrid: 6170706C65, bqual:
    62616E616E61]
    ...
    [16/02/22 12:28:54.883.15]  00000001  @2def8a7d
    c.i.mq.jmqi.JmqiXAResource
           --  !  rollback(Xid), The method 'xa_rollback' has failed
    with errorCode '-4'. [javax.transaction.xa.XAException]
    ...
    [16/02/22 12:29:00.505.1C]  00000001  @2def8a7d
    c.i.mq.jmqi.JmqiXAResource
           :::::::----+----+----+----+---  {  end(Xid,int) [format:
    1, gtrid: 6170706C65, bqual: 62616E616E61]
    [536870912(0x20000000)]
    ...
    [16/02/22 12:29:00.515.21]  00000001  @2def8a7d
    c.i.mq.jmqi.JmqiXAResource
           :::::::----+----+----+----+----  !  end(Xid,int), The
    method 'xa_end' has failed with errorCode '100'.
    [javax.transaction.xa.XAException]
    [16/02/22 12:29:00.516.00]  00000001  @2def8a7d
    c.i.mq.jmqi.JmqiXAResource
           :::::::----+----+----+----+----  {  rollback(Xid)
    [format: 1, gtrid: 6170706C65, bqual: 62616E616E61]
    ...
    [16/02/22 12:29:00.526.0N]  00000001  @2def8a7d
    c.i.mq.jmqi.JmqiXAResource
           ::::::::  !  rollback(Xid), The method 'xa_rollback' has
    failed with errorCode '-4'. [javax.transaction.xa.XAException]
    

Problem conclusion

  • The code has been updated to ensure that we correctly reduce the
    indent value in the trace when using the
    XAResource(JmqiXAResource) end and rollback methods and they
    throw exception back to the client application.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v9.1 LTS   9.1.0.12
    v9.2 LTS   9.2.0.6
    v9.3 LTS   9.3.0.1
    v9.x CD    9.3.1
    
    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 number

    IT39972

  • Reported component name

    IBM MQ BASE MP

  • Reported component ID

    5724H7271

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-02-15

  • Closed date

    2022-06-07

  • Last modified date

    2022-06-28

  • 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

    5724H7271

Applicable component levels

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910"}]

Document Information

Modified date:
29 June 2022