[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2666) ManagedPersistenceContext closed in a clustered environment

Kulvinder Singh (JIRA) jira-events at lists.jboss.org
Wed Mar 12 08:40:58 EDT 2008

    [ http://jira.jboss.com/jira/browse/JBSEAM-2666?page=comments#action_12402408 ] 
Kulvinder Singh commented on JBSEAM-2666:

I am also encountering the same problem in clustered enviornment. I am stuck up as functions are not working once it has passivated the session.

> ManagedPersistenceContext closed in a clustered environment
> -----------------------------------------------------------
>                 Key: JBSEAM-2666
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2666
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.1.GA
>            Reporter: Clint Popetz
>             Fix For: 2.1.x
>         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: http://jira.jboss.com/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the seam-issues mailing list