This week's book giveaway is in the Jobs Discussion forum.
We're giving away four copies of Java Interview Guide and have Anthony DePalma on-line!
See this thread for details.
The moose likes Websphere and the fly likes WebSphere DB2 Deadlock Exception. Reason code Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Java Interview Guide this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Products » Websphere
Bookmark "WebSphere DB2 Deadlock Exception. Reason code "2"" Watch "WebSphere DB2 Deadlock Exception. Reason code "2"" New topic

WebSphere DB2 Deadlock Exception. Reason code "2"

Karan Sinha

Joined: Apr 05, 2006
Posts: 19
I'm using IBM WebSphere Application Server Advanced Edition 4.0.1 and IBM UDB 7.0. Offlate i'm getting a continuous deadlock error in most of the system transactions. Pls provide with some inputs as its affecting many production users. [IBM][CLI Driver][DB2/6000] SQL0911N The current transaction has been rolled back because of a deadlock or timeout. Reason code "2". SQLSTATE=40001

Its not happening on a specific application, but on sparingly on all application for last 1 month. Is there a patch or fix from DB2 or WebSphere which solves this? I'm sure its not a generic error accross all users of this combination (WAS + IBM DB2 UDB). Any inputs and feedback is appreciated.

Note: The WebSphere App Server is configured to connect to DB2 using datasource.
Muthukris Bala

Joined: Oct 27, 2011
Posts: 1
Main reason for this error will be deadlock time out properties. To view this property value issue the following command:

Display Database Manager Configuration Settings:

Display Database level Configuration Settings

If dead lock time out value is -1 then change to either 60 or 120 sec based on your DB transaction.

n - number of sec.

For more information on dead lock please visit this link
I agree. Here's the link:
subject: WebSphere DB2 Deadlock Exception. Reason code "2"
It's not a secret anymore!