[hibernate-issues] [Hibernate-JIRA] Closed: (HHH-1254) Serialization of Sessions using JDBCTransactions with auto-flush/auto-close

[Steve Ebersole (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Steve Ebersole closed HHH-1254.
-------------------------------


Closing stale resolved issues

> Serialization of Sessions using JDBCTransactions with auto-flush/auto-close
> ---------------------------------------------------------------------------
>
>                 Key: HHH-1254
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1254
>             Project: Hibernate Core
>          Issue Type: Bug
>          Components: core
>            Reporter: Steve Ebersole
>            Assignee: Steve Ebersole
>            Priority: Minor
>             Fix For: 3.1
>
>
> When a Session (actually the JDBCContext) gets serialized, it "takes with it" its isTransactionCallbackRegistered variable.  The issue is that in the case of JDBCTransaction, this variable is really tied to the JDBCTransaction which does not get serialized along with the JDBCContext (as opposed to JTA-based transactions where this indicates the registration of the txn synch).  Thus upon deserialization, any new JDBCTransaction is not able to register as a callback since the JDBCContext thinks there is already one registered.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira