IBM Support

PM69045: WHEN A SIB MESSAGE ENGINE IS DELETED, THE PROXY QUEUES RELATED TO THE DELETED MESSAGING ENGINE ARE NOT CLEANED UP.

Fixes are available

8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
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.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.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

  • In a WebSphere Application Server environment, if there are
    two messaging engines, ME1 and ME2, communicating with each
    other, and if ME1 is deleted then the proxy queue related to
    the ME1 persists in the other messaging engine(ME2).
    
    The proxy queues persists even after multiple server restarts.
    One can observe that the proxy queue related to the deleted
    ME1 remains on ME2 from the message store dump taken at this
    point.
    

Local fix

  • No
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider     *
    *                  for IBM WebSphere Application Server        *
    *                  versions 7.0, 8.0 and 8.5                   *
    ****************************************************************
    * PROBLEM DESCRIPTION: In a WebSphere Application Server       *
    *                      environment, where we have two          *
    *                      Messaging engines communicating with    *
    *                      each other, if one of the Messaging     *
    *                      engines is deleted, then the proxy      *
    *                      queues related to that messaging        *
    *                      engine persist in the other messaging   *
    *                      engine even though the flag             *
    *                      'toBeDeleted' is set to 'true' on the   *
    *                      proxy queue. The proxy queues would     *
    *                      be used for the interaction between     *
    *                      two Messaging engine.                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    In a WebSphere Application Server environment, where we have
    two Messaging engines (ME) communicating with each other, if
    one of the Messaging engines is deleted, then the proxy queues
    related to that messaging engine persist in the other
    messaging engine even after multiple restarts. However, a
    message store dump taken at this point from the ME running
    would reveal that the flag 'toBeDeleted' is set to 'true' on
    the proxy queues related to the deleted Messaging engine.
    Also, from the traces, we see that the Subscription messages
    related to the deleted Messaging engine still persists.
    

Problem conclusion

  • The solution involves deleting the subscription messages
    related to the messaging engine which is deleted so that the
    proxy queue is gracefully deleted.
    
    Note: This fix does not address the scenario wherein the
    Messaging engine is already deleted and the relevant proxy
    queues are flagged 'toBeDeleted' as true. However, if the
    Messaging engine is deleted after applying this fix, it would
    help clearing the messages and hence allowing the graceful
    deletion of the related proxy queues.
    
    Since the ME related to the proxy queue is deleted, there
    would not be any interactions on the proxy queues. Hence the
    presence of the proxy queues of the deleted ME would not cause
    any problems and could be safely ignored. But if you wish to
    recover from the existing situation, the possible solution
    would be to drop the Messaging engines and create fresh.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 7.0.0.29, 8.0.0.6 and 8.5.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

    PM69045

  • 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

    2012-07-17

  • Closed date

    2012-11-29

  • Last modified date

    2013-02-12

  • 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

  • R800 PSY

       UP



Document information

More support for: WebSphere Application Server
Service Integration Technology

Software version: 7.0

Reference #: PM69045

Modified date: 12 February 2013