IBM Support

PM19281: KEYNOTFOUNDEXCEPTION LOGGED ON REPLICA CATALOG SERVER

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • KeyNotFoundException logged on replica catalog server
    Exception seen: Stack Dump =
    
    com.ibm.websphere.objectgrid.em.RollbackException: rolling back
    transaction, see caused by exception
        at
    com.ibm.ws.objectgrid.em.EntityTransactionImpl.commit(EntityTran
    sactionI
    mpl.java:148)
        at
    com.ibm.ws.objectgrid.catalog.placement.PlacementServiceImpl.tea
    rDownCon
    tainersInternal(PlacementServiceImpl.java:2458)
        at
    com.ibm.ws.objectgrid.catalog.placement.PlacementServiceImpl.ter
    minateCo
    ntainer(PlacementServiceImpl.java:2360)
        at
    com.ibm.ws.objectgrid.catalog.IDLPlacementServicePOA._invoke(IDL
    Placemen
    tServicePOA.java:297)
        at
    com.ibm.CORBA.poa.POAServerDelegate.dispatchToServant(POAServerD
    elegate.
    java:396
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of WebSphere eXtreme Scale.       *
    ****************************************************************
    * PROBLEM DESCRIPTION: Replica catalog server logs an          *
    *                      exception KeyNotFoundException for      *
    *                      the BalanceGrid:Container internal      *
    *                      data grid.                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A replica catalog server may get into an inconsistent state
    after a network brownout.  This inconsistent state causes
    KeyNotFoundException exceptions in to be found in the log
    files. You can resolve the problem by stopping and
    restarting the replica catalog server.
    

Problem conclusion

  • A future cumulative fix will correct the problem for WebSphere
    eXtreme Scale Versions 6.1.0.5, 7.0 and 7.1.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM19281

  • Reported component name

    XD EXTREME SCAL

  • Reported component ID

    5724J3402

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-07-27

  • Closed date

    2010-09-09

  • Last modified date

    2010-09-09

  • 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

    XD EXTREME SCAL

  • Fixed component ID

    5724J3402

Applicable component levels

  • R610 PSY

       UP

  • R700 PSY

       UP

  • R710 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSTVLU","label":"WebSphere eXtreme Scale"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
23 September 2020