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.