IBM Support

PM07111: UNABLE TO INSERT TWO ENTITIES IN DIFFERENT TABLES, BUT SHARE THESAME SUPERCLASS.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When two entity classes extending from the same super class, in
    case of the two objects of these two classes have exact same
    attributes of the super class and the first object is already
    persisted, when adding another oject, the JPA throws exception
    EJB threw an unexpected (non-declared) exception during
    invocation of method
    "updateEmployeeStateTaxAndGetFutureConflictsList" on bean
    "BeanId
    (eXpertsEAR#???????InternalServiceEJB.jar#??????Service,
    null)". Exception data:
    <openjpa-1.0.4-SNAPSHOT-r420667:829158M-OJ1350
    nonfatal store error> org.apache.openjpa.persistence.
    EntityExistsException: An object of type "com.???.????.model.
    ????.????.??????" with oid "com.???.????.model.common.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Feature Pack for EJB 3.0             *
    ****************************************************************
    * PROBLEM DESCRIPTION: Unable to insert two entities in        *
    *                      different tables, but share the same    *
    *                      superclass.                             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If an ID (primary key) is declared on a superclass of two
    entities the value must be unique for both of them. Whether
    the entities map to different tables is not taken into account.
    

Problem conclusion

  • To resolve this problem the persistence provider code has been
    updated and will only require the ID value to be unique for
    entities which share a table. More specifically the shared
    table must contain the ID (primary key).
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 6.1.0.31.  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

    PM07111

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-02-08

  • Closed date

    2010-03-16

  • Last modified date

    2010-03-31

  • 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 EJB3 FEATUR

  • Fixed component ID

    5724J0851

Applicable component levels

  • R610 PSY

       UP

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

Document Information

Modified date:
10 February 2022