Bug 900419 (JBPAPP6-875) - Test testContendedPessimisticLock(org.hibernate.ejb.test.lock.LockTest) hangs on some DBs
Summary: Test testContendedPessimisticLock(org.hibernate.ejb.test.lock.LockTest) hangs...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: JBPAPP6-875
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Hibernate
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: EAP 6.0.1
Assignee: Strong Liu
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBP...
Whiteboard:
Depends On:
Blocks: JBPAPP6-905
TreeView+ depends on / blocked
 
Reported: 2012-05-11 09:15 UTC by Madhumita Sadhukhan
Modified: 2014-06-28 12:35 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-04 09:32:39 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBPAPP6-875 0 None None None Never

Description Madhumita Sadhukhan 2012-05-11 09:15:11 UTC
project_key: JBPAPP6

This test hangs on Sybase 15.7, DB2-97, MS SQL2008 R1 and R2 but passes on other databases.


* IBM DB2 9.7,  Sybase ASE 15.7 - do not support apply lock timeout at statement level, only connection or global level
* Microsoft SQL Server 2008 R1, R2 - only support nowait clause

Comment 1 Zbyněk Roubalík 2012-06-05 10:50:20 UTC
Note for a jira verification: same problem is on mssql2008R1 and mssql2008R2

Comment 2 Zbyněk Roubalík 2012-06-07 09:22:11 UTC
Link: Added: This issue is a dependency of JBPAPP-9292


Comment 3 Zbyněk Roubalík 2012-06-08 16:05:31 UTC
https://hibernate.onjira.com/browse/HHH-7298

Comment 4 Jimmy Wilson 2012-08-14 15:02:14 UTC
Link: Added: This issue relates to JBPAPP-9693


Comment 5 Jimmy Wilson 2012-08-14 15:02:22 UTC
Link: Removed: This issue relates to JBPAPP-9693 


Comment 6 Zbyněk Roubalík 2012-10-04 09:32:39 UTC
Verified.

Comment 7 Anne-Louise Tangring 2012-11-13 20:07:42 UTC
Docs QE Status: Removed: NEW 



Note You need to log in before you can comment on or make changes to this bug.