PI74284: The JPA Container calls EntityManager.clear() instead of EntityManager.close() on cleanup

Fixes are available

APAR status

Closed as program error.

Error description

According to the JPA specification,
"The container may choose to pool EntityManagers: it instead
of
creating and closing in each case, it may acquire one from
its
pool and call clear() on it."

But when Liberty calls EntityManager.clear() method,
EclipseLink is not handling it properly and causing
unexpected
results.
&#160;

Local fix

Configure Liberty to stop pooling the EntityManager

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server Liberty - Java Persistence API       *
*                  (JPA)                                       *
****************************************************************
* PROBLEM DESCRIPTION: When running with the jpa-2.1 feature,  *
*                      the JPA Container calls                 *
*                      EntityManager.clear() on cleanup        *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When an EntityManager is ready to be cleaned up, the JPA
Container is calling EntityManager.clear() as part of pooling
the EntityManager. However, when using the jpa-2.1 feature,
EntityManager pooling is disabled. The JPA Container should not
be calling EntityManager.clear() since the EntityManager is not
being pooled. Instead, it should only call
EntityManager.close().

Problem conclusion

The JPA Container is no longer calling EntityManager.clear() on
EntityManager cleanup. Instead, the JPA Container calls
EntityManager.close() which properly cleans up the
EntityManager.

The fix for this APAR is currently targeted for inclusion in fix
pack 17.0.0.1.  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
PI74284
Reported component name
WAS LIBERTY COR
Reported component ID
5725L2900
Reported release
855
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-01-01
Closed date
2017-02-14
Last modified date
2017-02-14

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 LIBERTY COR
Fixed component ID
5725L2900

Applicable component levels

R855 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSD28V","label":"WebSphere Application Server Liberty Core"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022

Tips

PI74284: The JPA Container calls EntityManager.clear() instead of EntityManager.close() on cleanup

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

R855 PSY

Document Information

Share your feedback

Need support?