PI24575: USE OF JOINCOLUMN TARGETS TO ANOTHER JOINCOLUMN KEY EXPOSED AS AN ATTRIBUTE WILL CAUSE A CONSTRAINTVIOLATION EXCEPTION

8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• Using the following entities, when a simple single entry aCase
  -> aText -> aEvident instances are created, a
  ConstraintViolationException will be observed when this object
  tree is persisted.
  

Local fix

• No work around at this time
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: A JPA persist operation fails with a    *
  *                      ConstraintViolation                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  There existed a scenario where, given entities A, B, and C,
  where:
  A and B have a bidirectional *-to-One
  relationship where B is the owner of the relationship
  designating column X as the join column.
  B and C have a bidirectional *-to-one relationship where C is
  the owner of the relationship and designates B's X column as
  the referencedColumnName target.
  The above pattern can, under certain scenarios, produce a
  ConstaintViolation Exception during the running of the
  EntityManager.persist()
  operation.
  

Problem conclusion

• The JPA product has been corrected to manage this usage
  scenario.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.5.  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 is sysrouted FROM one or more of the following:

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

Fix information

• Fixed component name

  WEBSPHERE APP S

• Fixed component ID

  5724J0800

Applicable component levels

• R850 PSY

     UP