IBM Support

PM53035: WEBSPHERE APPLICATION SERVER HOSTING THE SERVICE INTEGRATION BUS MESSAGING ENGINE THROWS CWSIT0120E ERRORS

Fixes are available

7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • During startup, CWSIT0120E errors are logged in the
    SystemOut.log of WebSphere Application Server v7.0.x
    cluster hosting the Service Integration Bus messaging
    engine. Errors are also logged in the SystemOut.log of
    other cluster that is a member of the same BUS.
    
    
    Cluster A:
    CWSIT0118E: During an attempt to connect to a remote
    messaging engine {0} on bus {1}, incomplete information
    meant that it was not possible to validate the remote
    messaging engine''s identity
    
    
    CWSIT0034E: A messaging engine to messaging engine request
    failed in messaging engine {0} in bus {1} with reason: {2}.
    CWSIT0120E: It was not possible to validate the identity of
    the connecting messaging engine {0} on bus {1}
    
    
    
    Cluster B:
    CWSIT0119E: A connection attempt was made by remote
    messaging engine {0} on bus {1}, but incomplete information
    meant that it was not possible to validate the remote
    messaging engine''s identity
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider for *
    *                  IBM WebSphere Application Server 7.0        *
    ****************************************************************
    * PROBLEM DESCRIPTION: WebSphere Application Server startup    *
    *                      and shutdown operation take             *
    *                      considerable amount of time and thread  *
    *                      dumps indicate that there are WLM       *
    *                      threads that are processing SIB         *
    *                      code.Errors like CWSIT0120E are         *
    *                      observed in SystemOut and traces.       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When WLM notifies SIB about any processing that has to happen
    due to change in status of destination or any Messaging Engine
    SIB was using WLM thread to process the notification to
    completion. This leads the WLM threads to be held by SIB for a
    long time. In turn leading to contention of resources and
    shortage of WLM threads to process WLM work.
    

Problem conclusion

  • To fix the problem SIB code has been modified to absorb the
    notification from WLM and spawn new thread to process the work
    related to the notification. This results in faster release of
    WLM thread.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 7.0.0.25.  Please refer to the Recommended Updates
    page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM53035

  • Reported component name

    WAS SIB & SIBWS

  • Reported component ID

    620800101

  • Reported release

    300

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-11-29

  • Closed date

    2012-03-21

  • Last modified date

    2013-11-25

  • 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

    WAS SIB & SIBWS

  • Fixed component ID

    620800101

Applicable component levels

  • R300 PSY

       UP



Document information

More support for: WebSphere Application Server
Service Integration Technology

Software version: 7.0

Reference #: PM53035

Modified date: 25 November 2013