IBM Support

PK73754: RESETDESTINATION COMMAND ISSUED ON CORRUPT DESTINATION FAILS WITH EXCEPTION INVALIDOPERATION

Fixes are available

7.0.0.3: WebSphere Application Server V7.0 Fix Pack 3 for IBM i
7.0.0.3: WebSphere Application Server V7.0 Fix Pack 3 for AIX
7.0.0.3: WebSphere Application Server V7.0 Fix Pack 3 for HP-UX
7.0.0.3: Java SDK 1.6 SR4 Cumulative Fix for WebSphere Application Server
7.0.0.3: WebSphere Application Server V7.0 Fix Pack 3 for Solaris
7.0.0.3: WebSphere Application Server V7.0 Fix Pack 3 for Linux
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for AIX
7.0.0.3: WebSphere Application Server V7.0 Fix Pack 3 for Windows
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for IBM i
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Windows
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for HP-UX
7.0.0.5: Java SDK 1.6 SR5 Cumulative Fix for WebSphere Application Server
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Solaris
7.0.0.5: WebSphere Application Server V7.0 Fix Pack 5 for Linux
Java SDK 1.5 SR10 Cumulative Fix for WebSphere Application Server
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for IBM i
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for AIX
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Windows
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for HP-UX
7.0.0.7: Java SDK 1.6 SR6 Cumulative Fix for WebSphere Application Server
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Solaris
7.0.0.7: WebSphere Application Server V7.0 Fix Pack 7 for Linux
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for IBM i
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Windows
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for AIX
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for HP-UX
7.0.0.9: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Solaris
7.0.0.9: WebSphere Application Server V7.0 Fix Pack 9 for Linux
6.1.0.31: Java SDK 1.5 SR11 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for IBM i
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Windows
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for HP-UX
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for AIX
7.0.0.11: Java SDK 1.6 SR7 Cumulative Fix for WebSphere Application Server
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Solaris
7.0.0.11: WebSphere Application Server V7.0 Fix Pack 11 for Linux
6.1.0.33: Java SDK 1.5 SR12 FP1 Cumulative Fix for WebSphere
6.1.0.29: Java SDK 1.5 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for AIX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for HP-UX
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for IBM i
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Linux
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Solaris
7.0.0.13: WebSphere Application Server V7.0 Fix Pack 13 for Windows
7.0.0.13: Java SDK 1.6 SR8FP1 Cumulative Fix for WebSphere Application Server
6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
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
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
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

  • An attempt to reset a corrupt destination, using the
    resetDestination command results in the following error:
    com.ibm.ws.sib.processor.impl.exceptions.InvalidOperation
    Exception: CWSIP0005E: An internal messaging error occurred
    ACTIVE in com.ibm.ws.sib.processor.impl.indexes.statemodel.
    State, 1:223:1.12 at com.ibm.ws.sib.processor.impl.indexes.
    statemodel.State.reset
    
    This may follow a NullPointerException during messaging engine
    startup with the following stack:
    Exception = java.lang.NullPointerException
    Source = com.ibm.ws.sib.msgstore.cache.links.ItemLink.getItem
    probeid = 1:1899:1.212.1.3
    Stack Dump = java.lang.NullPointerException
     at
    com.ibm.ws.sib.processor.impl.indexes.AbstractDestinationIndex.
    corrupt(AbstractDestinationIndex.java:311)
     at
    com.ibm.ws.sib.processor.impl.DestinationManager.
    corruptDestination(DestinationManager.java:6832)
     at
    com.ibm.ws.sib.processor.impl.BaseDestinationHandler.setCorrupt(
    BaseDestinationHandler.java:2292)
     at
    com.ibm.ws.sib.processor.impl.store.items.MessageItem.restore(
    MessageItem.java:434)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider     *
    *                  for WebSphere Application Server version    *
    *                  6.0, version 6.1 and version 7.0.           *
    ****************************************************************
    * PROBLEM DESCRIPTION: Running the wsadmin resetDestination    *
    *                      command on a destination which has      *
    *                      been reported as being corrupt, can     *
    *                      result in the following exception:      *
    *                                                              *
    *                      com.ibm.ws.sib.processor.exceptions.    *
    *                      SIMPRuntimeOperationFailedException:    *
    *                      com.ibm.ws.sib.processor.impl.          *
    *                      exceptions.InvalidOperationException:   *
    *                                                              *
    *                      CWSIP0005E: An internal messaging       *
    *                      error occurred ACTIVE in                *
    *                      com.ibm.ws.sib.processor.impl.indexes.s *
    *                      tatemodel.State                         *
    *                                                              *
    *                      The destination remains corrupt.        *
    *                                                              *
    *                      For some types of corrupt destination,  *
    *                      messaging engine startup may also throw *
    *                      a NullPointerException as follows:      *
    *                      Exception =                             *
    *                      java.lang.NullPointerException          *
    *                      Source =                                *
    *                      com.ibm.ws.sib.msgstore.cache.links.    *
    *                      ItemLink.getItem                        *
    *                      probeid = 1:1899:1.212.1.3              *
    *                      Stack Dump =                            *
    *                      java.lang.NullPointerException          *
    *                      at                                      *
    *                      com.ibm.ws.sib.processor.impl.indexes.A *
    *                      bstractDestinationIndex.corrupt(Abstrac *
    *                      tDestinationIndex.java:311)             *
    *                      at                                      *
    *                      com.ibm.ws.sib.processor.impl.Destinati *
    *                      onManager.corruptDestination(           *
    *                      DestinationManager.java:6832)           *
    *                      at                                      *
    *                      com.ibm.ws.sib.processor.impl.BaseDesti *
    *                      nationHandler.setCorrupt(               *
    *                      BaseDestinationHandler.java:2292)       *
    ****************************************************************
    * RECOMMENDATION:  The resetDestination command is a recovery  *
    *                  tool to recreate a destination that has     *
    *                  been marked corrupt. It does not address    *
    *                  the root cause of the corrupt destination.  *
    *                                                              *
    *                  If you see a corrupt destination, the cause *
    *                  of the destination being marked corrupt     *
    *                  should be investigated. All logs and FFDCs  *
    *                  should be sent to IBM customer support for  *
    *                  analysis.                                   *
    ****************************************************************
    The resetDestination method on the SIBMessagingEngine MBean
    can only be used for a destination that is marked corrupt.
    A destination should remain marked as corrupt from the time
    CWSIK0027E log entry is displayed in the JVM log of the
    application server, until the messaging engine is restarted.
    
    In the problem case, an attempt to issue the wsadmin
    resetDestination method against a destination for which a
    CWSIK0027E had been output failed. It was found that the
    destination was in an active state rather than corrupt
    as had been reported. The destination state had been
    incorrect changed back to active, after the destination was
    marked as corrupt.
    
    The NullPointerException listed in this APAR can also prevent a
    destination from being marked corrupt. This was caused by the
    messaging engine attempting to mark a topic space destination
    corrupt before all necessary state had been initialized.
    

Problem conclusion

  • The fix prevents the destination from incorrectly returning to
    active state in the scenario reported in this APAR.
    
    InvalidOperationException exceptions continue to correctly be
    thrown if an attempt is made to reset a destination that has
    not been marked corrupt.
    
    The fix for this APAR is currently targeted for inclusion in
    fixpacks 6.0.2.35, 6.1.0.23 and 7.0.0.3.
    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

    PK73754

  • Reported component name

    PLAT MSG COM

  • Reported component ID

    620600101

  • Reported release

    200

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-10-14

  • Closed date

    2008-11-14

  • Last modified date

    2009-02-24

  • 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

    PLAT MSG COM

  • Fixed component ID

    620600101

Applicable component levels

  • R200 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 December 2021