PK78692: IN A 1:M RELATIONSHIP USING VERSIONED ENTITIES, ADDING A NEW ENTITY ON THE 1-SIDE INC'S ITS VERSION FIELD INAPPROPRIATELY.

Fixes are available

APAR status

Closed as program error.

Error description

In a one-to-oe relationship (that is, 1 customer to many
orders), the "one" side (customer) of a one-to-many
relationship has its version column updated when a new "many"
side entity (order) is created and added to the "one" side.
This leads to a version mismatch and a consequent
OptimisticLockException.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  V7.0                                        *
****************************************************************
* PROBLEM DESCRIPTION: OpenJPA generates unnecessary updates   *
*                      to version fields of entities in some   *
*                      cases.                                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When 2 entities are related to each other in a one-to-many
bidirectional relationship, adding an entry on the many side
causes OpenJPA to increment the version field of the one-side,
even though the one-side is unchanged. This update of the
version field causes many extra, unnecessary SQL UPDATE
statements to be issued. In moderately concurrent
applications, these updates to the version field may cause a
higher than normal number of OptimisticLockException
exceptions.

Problem conclusion

OpenJPA code was modified so that when traversing a
one-to-many relationship from the one side, we find out if
there is an inverse relationship from the many side. If there
is, then the update() call on the one side that bumps up the
version number is skipped. This call is made only when any
fields of the one side are actually found to be modified, in
which case the version number must be incremented.

The fix for this APAR is currently targeted for inclusion in
fixpack 7.0.0.3.

Temporary fix

Comments

APAR Information

APAR number
PK78692
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-01-14
Closed date
2009-02-17
Last modified date
2009-02-17

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

R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PK78692: IN A 1:M RELATIONSHIP USING VERSIONED ENTITIES, ADDING A NEW ENTITY ON THE 1-SIDE INC'S ITS VERSION FIELD INAPPROPRIATELY.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R700 PSY

Document Information

Share your feedback

Need support?