If you've used the HibernateTransactionAdvice CFC from the CFGroovy framework you may have witnessed weird behaviour after a failed transaction. I had neglected to close the active session after an error is encountered and the transaction rolled back. If you continued to use the Hibernate context after this happened for write operations you could encounter errors. The database was not affected, only Hibernate's in-memory caching.
I've added the line of code required to close out the active session when a transaction fails and is rolled back.
Comments are closed.