IBM Support

IC96519: WMQ FTE: ENABLING TRACE FOR THE WMQ CLASSES FOR JAVA PACKAGES RESULTS IN A LARGE AMOUNT OF DATA BEING WRITTEN TO TRACE FILES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In WebSphere MQ File Transfer Edition if trace is turned on
    with a trace string that includes the WebSphere MQ classes
    for Java client (for example "=all") then the generated trace
    files contain a large amount of data. This is due to all the
    bytes of
    each message being sent to the queue manager being dumped to
    the trace files. For a system with many file transfers or
    large file transfers this can lead to trace files that are
    wrapped and only
    cover a very short period of time. This can hinder problem
    diagnostic activities.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of WebSphere MQ File Transfer Edition
    7.0.4 and WebSphere MQ Managed File Transfer 7.5
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM SUMMARY:
    When trace was turned on that included the WebSphere MQ
    classes for Java package, large trace files would be produced as
    all data for each WebSphere MQ message would be output to the
    trace files. For an agent with many transfers or large transfers
    this would hinder the diagnosis of problems as the trace file
    would quickly wrap and key information was overwritten.
    

Problem conclusion

  • This APAR introduces a new agent property called
    traceMaxBytes. By default this property is set to 4096,
    meaning that the trace will contain up to the first 4096 bytes
    of each administrative message sent or received by the agent.
    This default property value can be overridden by defining an
    alternate value in the agent.properties file. If this property
    is set to -1 then the output will be unlimited.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.4.4
    v7.5       7.5.0.3
    
    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

    IC96519

  • Reported component name

    WMQ FILE TRANSF

  • Reported component ID

    5724R1000

  • Reported release

    704

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-10-01

  • Closed date

    2013-11-18

  • Last modified date

    2013-12-18

  • 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 FILE TRANSF

  • Fixed component ID

    5724R1000

Applicable component levels

  • R704 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEP7X","label":"WebSphere MQ File Transfer Edition"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.4","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
18 December 2013