[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-770) leaked connection in SFSB injected EntityManager after persist, passivate/activate, persist

[William DeCoste (JIRA)]

    [ http://jira.jboss.com/jira/browse/EJBTHREE-770?page=comments#action_12346167 ] 
            
William DeCoste commented on EJBTHREE-770:
------------------------------------------

After activation, when a call is made to the EntityManager that requires a connection (e.g. persist), the connection is leaked - it does not get closed at the end of persist, which leaves a handle on the connection, so when the tx commits, the connection is not released.

I have tracked the problem to the serialization/deserialization of org.hibernate.jdbc.ConnectionManager (hibernate 3.2.0.CR2). The releaseMode field is not serialized and when the CM is deserialized, the new CM is initialized with a null releaseMode - that looks like the root problem - this prevents the connection from being closed at the end of persist. 


> leaked connection in SFSB injected EntityManager after persist, passivate/activate, persist
> -------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-770
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-770
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC9 - FD
>            Reporter: William DeCoste
>         Assigned To: William DeCoste
>
> recreated in org.jboss.ejb3.test.stateful.RemoteUnitTestCase.testExtendedPersistencePassivation()

-- 
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