[hibernate-issues] [Hibernate-JIRA] Closed: (HHH-1541) incorrect transaction status reported

Steve Ebersole (JIRA) noreply at atlassian.com
Mon Mar 21 13:00:50 EDT 2011


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

Steve Ebersole closed HHH-1541.
-------------------------------


Closing stale resolved issues

> incorrect transaction status reported
> -------------------------------------
>
>                 Key: HHH-1541
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1541
>             Project: Hibernate Core
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.1.2
>         Environment: Hibernate 3.1.2, MySQL 5 (INNODB tables), MySQL 5 JDBC, SuSe 10.0 linux
>            Reporter: Peter Stein
>            Assignee: Steve Ebersole
>         Attachments: 1590595114-2823.zip
>
>
> Running the GenerateDeadlock example from chapter 9 of "Pro Hibernate 3" (www.apress.com) reveals that transaction status is not reported correctly. At no time is a HibernateException caught (to indicate deadlock) nor do the Transaction methods wasRolledBack() and wasCommitted() return correct values. wasRolledBack() is never true. Worse yet, wasCommitted() is actually true for transactions that were rolled back!

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

        


More information about the hibernate-issues mailing list