IBM Support

PI60131: UNAVOIDABLE CLASH DETECTED IN BUS LINK

Fixes are available

9.0.0.1: WebSphere Application Server traditional V9.0 Fix Pack 1
9.0.0.2: WebSphere Application Server traditional V9.0 Fix Pack 2
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
9.0.0.3: WebSphere Application Server traditional V9.0 Fix Pack 3
9.0.0.4: WebSphere Application Server traditional V9.0 Fix Pack 4
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
9.0.5.6: WebSphere Application Server traditional Version 9.0.5 Fix Pack 6

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Unavoidable Clash detected in bus link, whenever one side of
    the bus link has its messaging engine restarted and after which
    other side of the bus link has its server restarted.
    
    Details:
    
    Whenever messaging engine is restarted the listener that
    communicates the error is null since while restarting the
    messaging engine the TRM component gets initialized (TRM
    component intialization is reponsible for setting this listener)
    after starting the procesor component as ssen below from the
    traces:
    
    #########################################################
    [3/28/16 17:38:45:886 IST] 000008d0 SibMessage    I   [:]
    CWSID0016I:
    Messaging engine myME.server1-LinkBus is in state
    Stopped.
    [3/28/16 17:44:15:808 IST] 00000079 SibMessage    I   [:]
    CWSID0016I:
    Messaging engine myME.server1-LinkBus is in state
    Starting.
    [3/28/16 17:44:16:152 IST] 00000079 MPIO          >  init
    (com.ibm.ws.sib.processor.io.MPIO) [:] Entry
                                     <null>
    
    com.ibm.ws.sib.trm.topology.RoutingManagerImpl@4f79f306
    [3/28/16 17:44:16:761 IST] 00000079 MessageProces <  start
    (com.ibm.ws.sib.processor.impl.MessageProcessor) [:] Exit
    [3/28/16 17:44:16:761 IST] 00000079 TrmMeMainImpl >  start
    (com.ibm.ws.sib.trm.TrmMeMainImpl) [:] Entry
                                     0
    #########################################################
    
    Since this listener is null whenever the other messaging engine
    communicates error to this messaging engine, it is unable to
    invalidate
    the messaging connection which is resulting in the clash
    observed below:
    
    #########################################################
    [3/28/16 17:44:51:933 IST] 00000085 CommonMeHandS 3
    (com.ibm.ws.sib.trm.attach.CommonMeHandShake) [:] Clash
    detected.
    #########################################################
    
    The clash doesn't seem to get resolved until the other side of
    the link is restarted.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: In a WebSphere environment using        *
    *                      Service Integration bus, the bus link   *
    *                      doesn't come up whenever the server on  *
    *                      one side of the link is restarted after *
    *                      messaging engine on another side has    *
    *                      been restarted.                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    While using the Service Integration Bus of WebSphere
    Application Server, a clash detected message is observed when
    trace is enabled in a scenario where the bus link is present
    and when the server on one side of the bus link is restarted
    after restarting the messaging engine on the other side of the
    bus link. Whenever the messaging engine is restarted the
    listener that communicates the error is null since while
    restarting the messaging engine the TRM component gets
    initialized (TRM component initialization is responsible for
    setting this listener) after starting the processor component.
    The following message is observed when trace is enabled:
    [3/28/16 17:44:51:933 IST] 00000085 CommonMeHandS 3
    (com.ibm.ws.sib.trm.attach.CommonMeHandShake) [:] Clash
    detected.
    The clash doesn't get resolved until the other side of the
    link is restarted.
    

Problem conclusion

  • The code has been fixed to ensure that the listener that
    communicates the error isn't null which ensures that the bus
    link starts successfully whenever the messaging engine is
    restarted.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.5.5.11 and 9.0.0.2 .  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

    PI60131

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-04-04

  • Closed date

    2016-07-11

  • Last modified date

    2016-07-11

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R850 PSY

       UP

  • R900 PSY

       UP

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850"}]

Document Information

Modified date:
17 June 2021