PM23607: INVALIDCLASSEXCEPTION IN DYNACACHE WHEN USING DIFFERENT JDK LEVELS FOR WEBSPHERE AND GRID TIER.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Getting this exception during invalidation.
    
    Stack Dump =
    com.ibm.websphere.objectgrid.ObjectGridRuntimeException:
    org.omg.CORBA.INTERNAL: An internal error happened processing
    the
    request  vmcid: 0x0  minor code: 0  completed: No
     at
    com.ibm.ws.objectgrid.client.ORBClientCoreMessageHandler.sendMes
    sage
    (ORBClientCoreMessageHandler.java:537)
     at
    com.ibm.ws.objectgrid.client.ORBClientCoreMessageHandler.sendMes
    sage
    (ORBClientCoreMessageHandler.java:978)
     at com.ibm.ws.objectgrid.client.RemoteTransactionCallbackImpl.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All eXtreme Scale users who have their      *
    *                  WebSphere Application Server environment    *
    *                  configured to use eXtreme Scale as          *
    *                  their dynamic cache provider.               *
    ****************************************************************
    * PROBLEM DESCRIPTION: When using different versions of the    *
    *                      JDK,                                    *
    *                      an InvalidClassException exception      *
    *                      results during serialization.           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The serialVersionUID variable was not defined in the class. If
    JDK levels between client and server are not the same,
    InvalidClassException exception results during
    serialization. The product code has been updated to include the
    serialVersionUID variable to correct this problem.
    

Problem conclusion

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

Temporary fix

Comments

APAR Information

  • APAR number

    PM23607

  • 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-09-30

  • Closed date

    2010-10-01

  • Last modified date

    2010-10-01

  • 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

  • R700 PSY

       UP

  • R710 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

WebSphere eXtreme Scale
General

Software version:

6.1

Reference #:

PM23607

Modified date:

2010-10-01

Translate my page

Machine Translation

Content navigation