IBM Support

IT09436: WEBSPHERE MQ CLASSES FOR JAVA/JMS PRODUCES EXCESSIVE TRACE WHEN RECEIVING AND INTERPRETING LARGER MQ MESSAGES

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

  • When trace is enabled for the WebSphere MQ classes for Java/JMS,
    a lot of information is output to the trace log when the classes
    are performing the analysis of data received from the queue
    manager.
    
    If the messages being received are of significant size (more
    than a few KB), the trace log contains a significant amount of
    duplicated data.
    
    The consequence of this is that the trace log is considerably
    larger than it needs to be, which can reduce application
    performance, and consume a lot of storage on the system.
    This issue also affects MQ applications running within the
    WebSphere Application Server 8.5 and 8.5.5 environments.
    

Local fix

  • <html></html>
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of WebSphere MQ classes for Java/JMS, including the
    Application Server 8.5 and 8.5.5 who are collecting trace of the
    WebSphere MQ Resource Adapter component, for example by using
    the trace string:
    
    *=info:JMSApi=all:JMSServer=all:Messaging=all:JMS_WASTraceAdapte
    r=all:com.ibm.mq.*=all:jmsApi=all
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    Prior to the use of WebSphere MQ Resource Adapter v7.1 within
    the WebSphere Application Server (corresponding to versions
    earlier than 8.5), the data-buffers containing the message
    content data were not printed into the trace files, when using
    the WebSphere MQ Resource Adapter trace strings.
    
    As a result of this additional printout, the trace files are
    significantly larger.  This creates several challenges,
    including:
    
    (1) Reduction in performance when trace is enabled
    
    (2) More filesystem storage space is required to collect the
    trace
    
    (3) Longer times to transfer the data into IBM Support
    
    (4) Increases the verbosity of the trace making analysis slower
    
    
    Some of the WebSphere MQ Resource Adapter trace points are
    superfluous, for example printing out the same data-buffer
    repeatedly over multiple trace points where there has been no
    modification to the data.  These trace points are not needed for
    analysis and offer very little benefit.
    

Problem conclusion

  • The superfluous trace data has been removed.
    
    With this change, the reduction in trace size is of the order of
    5 to 10% when consuming messages which are 1MB in size.
    
    
    Note that there is a related APAR within the WebSphere
    Application Server product which limits the size of the
    data-buffers being printed to 2KB.  This APAR is PI43084:
    
        http://www.ibm.com/support/docview.wss?uid=swg1PI43084
    
    
    This second APAR can have a more significant impact into the
    reduction of trace size.  For example, in a test run with trace
    enabled consisting of consuming 10 messages (each 1MB in size)
    with an Activation Specification from a MQ queue, including
    starting and stopping the application server, the change in size
    of the trace log is as follows:
    
    (1) Neither APAR applied:
           Trace size = 188MB
    
    (2) APAR PI43084 applied:
          Trace size = 34MB
    
    (3) APAR PI43084 + IT09436 applied:
          Trace size = 31MB
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.1       7.1.0.8
    v7.5       7.5.0.7
    
    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

    IT09436

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    710

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-06-12

  • Closed date

    2016-02-26

  • Last modified date

    2016-02-26

  • 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

    WMQ WINDOWS V7

  • Fixed component ID

    5724H7220

Applicable component levels

  • R710 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCPQ63","label":"APAR \/ Maintenance"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"710","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
26 February 2016