IBM Support

PI93516: JMS DESTINATION MARKED TOBEDELETED CANNOT BE DESTROYED AND RECREATED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After deleting the JMS destinations and ME was stopped before
    the deletion completes, if we perform a new deployment of the
    application, the application cannot send/publish messages to
    the destination.
    

Local fix

  • Manually delete the destination and recreate them before
    stopping ME.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users SIB JMS messaging engines in      *
    *                  IBM WebSphere Application Server            *
    ****************************************************************
    * PROBLEM DESCRIPTION: Stopping a SIB JMS Messaging Engine     *
    *                      whilst a JMS destination is being       *
    *                      deleted can prevent it, once            *
    *                      recreated, being usable.                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If the configuration for a SIB JMS Messaging Engine is
    modified to delete a JMS destination, and that messaging
    engine is then rapidly stopped (before the destination
    deletion has complete), that destination may be recorded as
    being "to be deleted".
    In this condition, if the configuration is further modified
    (whilst the messaging engine is stopped) to restore the JMS
    destination, and then the Messaging Engine restarted, the
    destination is incorrectly reconstituted with this "to be
    deleted" state preserved.
    This preserved state prevents the destination from receiving /
    producing any messages.
    

Problem conclusion

  • The fix was to recognise this situation, and to discard the
    "to be deleted" destination information read from the message
    store, so it may be replaced with the new, "restored"
    destination from the now current configuration.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.5.14 and 9.0.0.8.
    
    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

    PI93516

  • 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

    2018-02-07

  • Closed date

    2018-06-20

  • Last modified date

    2018-06-20

  • 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

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCVS22","label":"General"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
20 June 2018