IBM Support

IC68112: Tracing of a .NET thread in a COM+ context is incomplete - 'xtrTurnOffTrace: Turning off trace for this thread' is visible

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • WebSphere MQ successfully captures trace from a .NET thread
    acting under a COM+ context. However, after completing the
    MQCONNX request in the native layer, the trace for that thread
    is disabled. No further trace for that thread is found in the
    trace file even though MQ API requests continue to be issued.
    'xtrTurnOffTrace: Turning off trace for this thread' is printed
    out in the trace after the MQCONN call returns.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Any users of WebSphere MQ running unmanaged .NET applications
    in a COM+ context.
    
    Platforms affected:
    Windows
    
    ****************************************************************
    PROBLEM SUMMARY:
    The problem was caused due to an incorrect reference count
    being used to determine how many times the thread had
    registered against common services. As a result, the common
    services library determined that the thread was no longer
    registered and therefore no longer wanted to trace even though
    the actual reference count should still have been positive.
    

Problem conclusion

  • WebSphere MQ was modified to ensure that the reference count
    was incremented and decremented correctly to keep track of
    registrations by application threads to WebSphere MQ common
    services and tracing functionality.
    
    | MDVREGR 7.0.1-WS-MQ-Windows-FP0002        |
    | MDVREGR 7.0.1-WS-MQ-Windows-FP0001        |
    | MDVREGR 7.0-WS-MQ-Windows-RP0001          |
    
    
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
                       v7.0
    Platform           Fix Pack 7.0.1.3
    --------           --------------------
    Windows            U200320
    
    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

    IC68112

  • Reported component name

    WMQ WINDOWS V7

  • Reported component ID

    5724H7220

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-04-22

  • Closed date

    2010-05-10

  • Last modified date

    2011-02-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 WINDOWS V7

  • Fixed component ID

    5724H7220

Applicable component levels

  • R700 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDEZSF","label":"IBM WebSphere MQ Managed File Transfer for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
31 March 2023