IBM Support

PI21325: JVM PANIC FOLLOWED BY ILLEGALSTATEEXCEPTION DUE TO TIMING ISSUE WHEN MUTILPLE THREADS ATTEMPT TO PERSIST LARGE MESSAGES

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • JVM panic followed by an illegal state exception due to timing
    issue when there is an attempt to persist large messages by
    multiple applkication threads.
    
    Following exception stack is noticed in the SystemOut.log:
    -----------------------------------
    SpillDispatch 1   Unexpected exception caught in
    SpillDispatcher thread!  java.lang.IllegalStateException:
    CWSIS1527E: A persistable object is in an incorrect state:
    operations begun count: 0, operations completed
    count: 2.
    at
    com.ibm.ws.sib.msgstore.persistence.impl.Token.persistableOperat
    ionCancelled(Token.java:674)
    at
    com.ibm.ws.sib.msgstore.persistence.impl.CachedPersistableImpl.p
    ersistableOperationCancelled(CachedPersistableImpl.java:94)
    at
    com.ibm.ws.sib.msgstore.persistence.dispatcher.SpillDispatcher$S
    pillDisp
    atcherThread.batchCancelled(SpillDispatcher.java:1903)
    at
    com.ibm.ws.sib.msgstore.persistence.dispatcher.SpillDispatcher$S
    pillDispatcherThread.run(SpillDispatcher.java:754)
    ..
    ..
    
    Spill Dispatcher has been marked as unhealthy as there was an
    inconsistency between "number of tasks begun" and the "number
    of tasks
    completed", because of this reason it did not accept any more
    new tasks.
    
    XidParticipan <  prepare
    (com.ibm.ws.sib.msgstore.transactions.XidParticipant)
    [:/f5dcea9e] Exit
    
    com.ibm.ws.sib.msgstore.RollbackException: CWSIS1002E: An
    unexpected exception was caught during transaction completion.
    Exception:  com.ibm.ws.sib.msgstore.PersistenceException:
    CWSIS1578E: The spill dispatcher cannot accept work.
    
    (3) Because of this inconsistency, there was a JVM panic
    followed by a local error.
    
    [6/30/14 11:11:21:450 EDT] 00000010 MessageStoreI >
    reportLocalError
    (com.ibm.ws.sib.msgstore.impl.MessageStoreImpl)
    [wmserver_ILS_QUEUE_CONNECTOR.sib:avwoolapp-02Node01.wmserver-wm
    server_I LS_QUEUE_CONNECTOR.sib/896df08b] Entry
    
    SystemOut     O Panic:component requested panic from isAlive
    SystemOut     O java.lang.RuntimeException: emergencyShutdown
    called:
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of the default messaging provider     *
    *                  for                                         *
    *                  IBM WebSphere Application Server V8.0 and   *
    *                  V8.5.                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION: JVM panic followed by an                *
    *                      IllegalStateException due to timing     *
    *                      issue when there is a delay in          *
    *                      persisting messages.                    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Whenever a new persisting task comes in for the
    SpillDispatcher, it is getting inserted in the head position
    which is ahead of other tasks in the task list.
    During completion of the task, an existing approach just
    removes the first element from the task list instead of
    getting an actual position of the task id and removing it.
    If persisting an existing task takes more time, it is possible
    that another new task gets added on top of the current running
    task in the task list. After the completion of the current
    persistence task, a new recent task which of on top of the
    list gets removed (instead of the actual task) from the task
    list. This would lead an incosistency between "operations
    begun count" and "operations completed count".
    Note:
    This problem is applicable for persisting a reliable
    non-persistent or express non-persistent message with the
    combination of either large message or any delay in persisting
    a message into the message store.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    PI21325

  • Reported component name

    WAS SIB & SIBWS

  • Reported component ID

    620800101

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-07-03

  • Closed date

    2014-09-25

  • Last modified date

    2014-11-04

  • 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

  • R850 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":"8.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 April 2022