[hibernate-issues] [Hibernate-JIRA] Resolved: (HHH-5013) the previous select query should not to hold locks in TypeParameterTest#testSave

Strong Liu (JIRA) noreply at atlassian.com
Tue Mar 16 01:20:49 EDT 2010


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

Strong Liu resolved HHH-5013.
-----------------------------

    Resolution: Fixed

> the previous select query should not to hold locks in TypeParameterTest#testSave
> --------------------------------------------------------------------------------
>
>                 Key: HHH-5013
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5013
>             Project: Hibernate Core
>          Issue Type: Bug
>          Components: testsuite
>    Affects Versions: 3.5.0-CR-2
>            Reporter: Strong Liu
>            Assignee: Strong Liu
>             Fix For: 3.5.0.Next
>
>
> Hi Strong Liu,
>  
> I'm getting "lock timeout" in the org.hibernate.test.typeparameters.TypeParameterTest testSave test.  Within testSave and testLoading a session and transaction is initiated to create a Widget object, persist it and then closed.  A second session is started with a transaction to query the Widget attributes followed by a call to deleteData while this parent session holds physical database locks.
>  
> Within the deleteData method a new session with its own transaction is created which waits for locks held by the parent resulting in a deadlock.
>  
> I presume the test is expecting the previous select query not to hold locks?

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