IBM Support

IC96105: FDC FILE GENERATED WHEN INITIALISING WMQ COMMONSERVICES TRACER DURING JBOSS APPLICATION SERVER START

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using the WebSphere MQ Resource Adapter version 7.5.0.1
    (and higher),
    the following Failure Data Capture (FDC) file is generated
    during server startup:
    
    Product    :- ProductName
    Date/Time   :- Mon Sep 23 14:56:00 BST 2013
    System time   :- 1379944560905
    Operating System  :- Linux
    UserID    :- user
    Java Vendor   :- IBM Corporation
    Java Version   :- 2.6
    
    Source Class   :-
    com.ibm.msg.client.commonservices.trace.Trace$3
    Source Method  :- onCSIInitialize
    ProbeID    :- Failed to initialize CSI from Trace listener
    Thread    :- name=MSC service thread 1-1 priority=5 group=main
    ccl=ModuleClassLoader for Module "deployment.wmq.jmsra.rar:main"
    from Service Module Loader
    Data
    ----
    | Exception :- ExceptionDepth is 2
    | Exception :-
    | | Cause:1 :- com.ibm.msg.client.commonservices.CSIException:
    The call could not be completed because CommonServices has not
    been initialized.
    | | Message:1 :- The call could not be completed because
    CommonServices has not been initialized.
    | | StackTrace:1 :-
    com.ibm.msg.client.commonservices.CSIException: The call could
    not be completed because CommonServices has not been
    initialized.
    | |  at
    com.ibm.msg.client.commonservices.trace.Trace.initialize(Trace.j
    ava:2236)
    | |  at
    com.ibm.msg.client.commonservices.trace.Trace$3.onCSIInitialize(
    Trace.java:2300)
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects all users of the WebSphere MQ Resource
    Adapter version 7.5.0.1 and above.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM SUMMARY:
    The Failure Data Capture (FDC) file identified by ProbeID
    "Failed to initialize CSI from Trace listener" was being
    incorrectly generated during initialisation of the WebSphere
    MQ CommonServices Tracer. The FDC file was generated because the
    code received a callback before all prerequisite resources
    were initialized. Attempting to handle this callback prematurely
    caused the error reported in the FDC file.
    
    This is a result of the changes introduced by IV14464 in fixpack
    7.5.0.1.
    

Problem conclusion

  • The WebSphere MQ CommonServices Tracer code has been updated
    to be tolerant to multiple callbacks, and will only proceed when
    all prerequisite resources have been initialized. The FDC
    file, identified by ProbeID "Failed to initialize CSI from Trace
    listener", is now only generated after a genuine failure to
    initialise the WebSphere MQ CommonServices Tracer when all
    prerequisite resources have already been successfully
    initialised.
    
    
    | MDVREGR 7.5.0-WS-MQ-AixPPC64-FP0001 |
    | MDVREGR 7.5.0-WS-MQ-HpuxIA64-FP0001 |
    | MDVREGR 7.5.0-WS-MQ-HpuxPaRISC64-FP0001 |
    | MDVREGR 7.5.0-WS-MQ-LinuxIA32-FP0001 |
    | MDVREGR 7.5.0-WS-MQ-LinuxPPC64-FP0001 |
    | MDVREGR 7.5.0-WS-MQ-LinuxS390X-FP0001 |
    | MDVREGR 7.5.0-WS-MQ-LinuxX64-FP0001 |
    | MDVREGR 7.5.0-WS-MQ-SolarisSparc64-FP0001 |
    | MDVREGR 7.5.0-WS-MQ-SolarisX64-FP0001 |
    | MDVREGR 7.5.0-WS-MQ-Windows-FP0001 |
    
    | MDVREGR 7.5.0-WS-MQ-AixPPC64-FP0002 |
    | MDVREGR 7.5.0-WS-MQ-HpuxIA64-FP0002 |
    | MDVREGR 7.5.0-WS-MQ-HpuxPaRISC64-FP0002 |
    | MDVREGR 7.5.0-WS-MQ-LinuxIA32-FP0002 |
    | MDVREGR 7.5.0-WS-MQ-LinuxPPC64-FP0002 |
    | MDVREGR 7.5.0-WS-MQ-LinuxS390X-FP0002 |
    | MDVREGR 7.5.0-WS-MQ-LinuxX64-FP0002 |
    | MDVREGR 7.5.0-WS-MQ-SolarisSparc64-FP0002 |
    | MDVREGR 7.5.0-WS-MQ-SolarisX64-FP0002 |
    | MDVREGR 7.5.0-WS-MQ-Windows-FP0002 |
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    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

    IC96105

  • Reported component name

    WMQ BASE MULTIP

  • Reported component ID

    5724H7241

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-09-19

  • Closed date

    2013-10-17

  • Last modified date

    2013-11-05

  • 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 BASE MULTIP

  • Fixed component ID

    5724H7241

Applicable component levels

  • R750 PSY

       UP

[{"Line of Business":{"code":"LOB36","label":"IBM Automation"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5"}]

Document Information

Modified date:
23 September 2021