PK80331: FIELD INJECTION OF A JPA PERSISTENCECONTEXT MY RESULT IN AN INVALIDSTATEEXCEPTION UNDER HEAVY LOAD

Fixes are available

APAR status

Closed as program error.

Error description

Injecting a PersistenceContext (via Java annotations or XML)
into a field within a SessionBean may result in the following
exception in a high volume/multi-threaded scenario:

[1/7/09 18:21:28:640 EST] 00000028 ExceptionUtil E   CNTR0020E:
EJB threw an unexpected (non-declared) exception during
invocation of method "getBatchJob" on bean
"BeanId(BatchEAR#PayrollSystem.jar#BatchJobService, null)".
Exception data: <openjpa-1.0.3-SNAPSHOT-r420667:646455 fatal
user error>

org.apache.openjpa.persistence.InvalidStateException: The
context has been closed.  The stack trace at which the context
was closed is held in the embedded exception.


FailedObject: java.lang.IllegalStateException at

org.apache.openjpa.kernel.BrokerImpl.assertOpen(BrokerImpl.java:
4303)
at
org.apache.openjpa.kernel.QueryImpl.assertOpen(QueryImpl.java:16
23)
at
org.apache.openjpa.kernel.QueryImpl.setUnique(QueryImpl.java:465
)
at
org.apache.openjpa.kernel.DelegatingQuery.setUnique(DelegatingQu
ery.java:331)
at
org.apache.openjpa.persistence.QueryImpl.getSingleResult(QueryIm
pl.java:302) "

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  Feature Pack for EJB 3.0                    *
****************************************************************
* PROBLEM DESCRIPTION: IllegalStateException or                *
*                      ConcurrentModificationException can     *
*                      occur when an application with JPA      *
*                      entity beans is under load.             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Applications with Java Persistence API (JPA) entity beans that
inject PersistenceContexts on fields within Session beans may
incur IllegalStateExceptions or
ConcurrentModificationExceptions when the application is under
heavy load.

Problem conclusion

This problem was caused by the fact that an instance
of an EntityManager was tied to a Stateless
Session Bean instance due to the injection of a persistence
context into a field within the Stateless Session Bean.

The problem occurred because the stateless session bean
instance was pooled and re-used by another thread prior to the
first thread finishing afterCompletion processing.

The problem was resolved by changing the code such that the
session bean instance was not physically tied to a particular
entity manager instance beyond the scope of the unit of work
and that the entity manager instance would be cleaned up or
pooled when the unit of work completed.

The fix for this APAR is currently targeted for inclusion in
fixpack 7.0.0.3.  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
PK80331
Reported component name
WAS EJB3 FEATUR
Reported component ID
5724J0851
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2009-02-10
Closed date
2009-03-02
Last modified date
2009-03-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
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"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK80331: FIELD INJECTION OF A JPA PERSISTENCECONTEXT MY RESULT IN AN INVALIDSTATEEXCEPTION UNDER HEAVY LOAD

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

R610 PSY

Document Information

Share your feedback

Need support?