IBM Support

PM30105: INVALIDSTATEEXCEPTION WHEN RUNNING OPENJPA APPLICATION

Fixes are available

7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
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
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
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 InvalidStateException exception is caused as follows:
    
    org.apache.openjpa.persistence.InvalidStateException: Attempt
    to change a primary key field of an instance that already has
    a final object id. Only new, unflushed instances whose id you
    have not retrieved can have their primary keys changed.
    FailedObject:
    org.apache.openjpa.persistence.xs.AccountingHierarchyRate-TESTIN
    G::1
    at
    org.apache.openjpa.kernel.StateManagerImpl.assertNoPrimaryKeyCha
    nge(StateManagerImpl.java:2086)
    at
    org.apache.openjpa.kernel.StateManagerImpl.settingObjectField(St
    ateManagerImpl.java:2020)
    
    
    The problem is related to this OpenJPA JIRA:
    https://issues.apache.org/jira/browse/OPENJPA-1911
    

Local fix

  • N/A.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V7.0.0 who attempt to merge (that    *
    *                  is, EntityManager.merge) a Java             *
    *                  Persistence API (JPA) entity which has      *
    *                  been serialized and contains a compound     *
    *                  primary key (that is, uses @IdClass).       *
    *                                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: InvalidStateException can occur when    *
    *                      merging a serialized JPA entity which   *
    *                      contain a compound primary key.         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Take an entity which contains a compound primary key,
    specifically the entity uses @IdClass.  When an instance of
    this entity is serialized (for example, part of a remote method
    call), if a user attempts to merge the instance (that is,
    EntityManager.merge), it could result in an
    InvalidStateException.
    

Problem conclusion

  • With this fix, code has been added to ensure that a JPA entity
    which contains a compount primary key can be properly merged
    after that entity has been serialized.
    
    The fix for this APAR is currently targeted for
    inclusion in Service Level (Fix Pack) 7.0.0.19 of WebSphere
    Application Server version 7.0.0.
    
    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

    PM30105

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-01-07

  • Closed date

    2011-03-23

  • Last modified date

    2011-03-23

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    PM30346

Fix information

  • Fixed component name

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM30105

Modified date: 23 March 2011