It's not a secret anymore!
The moose likes JDBC and Relational Databases and the fly likes DeadLock or Timeout Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Databases » JDBC and Relational Databases
Bookmark "DeadLock or Timeout" Watch "DeadLock or Timeout" New topic

DeadLock or Timeout

Kumar Godugu

Joined: Jul 18, 2005
Posts: 1
Hi All,
I am performing around 30 transactions, My requirement is that either I need to commit all Transactions or I need to roll back all if any of them fails. All Transactions are executing properly but before just committing it throwing the following exception. [IBM][CLI Driver][DB2/6000] SQL0911N The current transaction has been rolled back because of a deadlock or timeout. Reason code "68". SQLSTATE=40001

If I use Connection.setAutoCommit(true) before starting of Transactions, then I can able to executing all the transactions success fully.I am using servltes and Tomcat server.

Please help me to solve this.
Adeel Ansari
Ranch Hand

Joined: Aug 15, 2004
Posts: 2874
Try frequent commits.

Webopedia Definition of Deadloack
I agree. Here's the link:
subject: DeadLock or Timeout
It's not a secret anymore!