Are you using the same userid for the stress test? If you are that would
be an issue, otherwise put an index on user_login_id.

Dan Callahan IT Specialist
603-472-4121 t/l 525-4121
[Email address protected]




"yjchong"
<db2udbdba-ezmlms
hield-x63830027.x To
[Email Address Removed] "LazyDBA Discussion"
a.com> <[Email address protected]
cc
02/27/2005 10:57
PM Subject
Deadlock during concurrent update










Dear all,

I have run a series of load test with 80 users in a web application. Some
user can't login to the application with
the deadlock error :

:[IBM][CLI Driver][DB2/NT] SQL0911N The current transaction has been
rolled back because of a deadlock or timeout. Reason code "2".
SQLSTATE=40001

I found that in the java application code:

strQuery = "UPDATE USER_LOGIN SET my_timestamp_type_column = CURRENT
TIMESTAMP, my_int_column = 0 WHERE USER_LOGIN_ID = ?";
....
prepareStatement(strQuery);
myStmt.setString(1, strUserId);
...
iUpdated = myStmt.executeUpdate(); //Deadlock error occured during
concurrent test.


Any constructive solution for that problem?

Many thanks.

Rgds,
John


---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html



DB2 & UDB email list listserv db2-l LazyDBA home page