JDBC deadlocks 
Author Message
 JDBC deadlocks

Hi, All!

Platform: server-side java w/JDBC-ODBC bridge.
Transaction isolation level: READ_COMMITED.

Have a very weird problem here. Happens on both on MS SQL 6.5 an 7.0,
when one application connection (A) is inside the fairly long
transaction, and the other connection (B) tries to SELECT (only!) from
the tables locked by that transaction, transaction (!) stops executing
until the second query from A does not timeout and pull out.

The same application on Oracle seems working fine.

Could it be the JDBC thread synchronization problem? I.e. while one
connection is waiting on the blocked table, nothing else can execute?

Any help will be greatly appreciated.


* Sent from RemarQ http://www.***.com/ The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!

Tue, 23 Apr 2002 03:00:00 GMT
 [ 1 post ] 

 Relevant Pages 

1. JDBC + DeadLock Problem -> no correct rollback

2. jdbc deadlock simulation ?

3. Unexplained deadlock...possible JDBC driver bug

4. JDBC: Possible deadlock in resultset.next()?

5. JDBC: Possible deadlock in resultset.next()?

6. Unexplained deadlock...possible JDBC driver bug (again).

7. How to avoid JDBC allocation Deadlock

8. Deadlocked by Deadlocks

9. Deadlock situtation (deadlock victim) - help needed!!

10. jdbc-odbc bridge or jdbc native driver ?

11. JDBC, Blob data, Oracle JDBC

12. JDBC-PreparedStatement (JDBC-ODBC) problem with MS SQLServer 7

Powered by phpBB® Forum Software