]
Pete Muir updated JBSEAM-2666:
------------------------------
Fix Version/s: (was: The future)
2.1.0.BETA2
ManagedPersistenceContext closed in a clustered environment
-----------------------------------------------------------
Key: JBSEAM-2666
URL:
http://jira.jboss.com/jira/browse/JBSEAM-2666
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.0.1.GA
Reporter: Clint Popetz
Fix For: 2.1.0.BETA2
Attachments: mpc-passivate.diff
ManagedPersistenceContext, upon passivation, checks to see if the entity manager is
dirty, and if not, closes it. I presume this is intended as an optimization. But in a
clustered environment, where a snapshot of the session is taken upon each request that
dirties the session, passivation will occur frequently within a conversation. In this
case, the entity manager is frequently closed and recreated upon the next request, and
entities in conversational beans become detached, and all sorts of bad things happen when
I try to use them in the new session.
I think that to preserve the promise of long conversations, we have to keep the
persistence context open across passivation, regardless of whether it's dirty.
The attached patch removes the entityManager close().
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: