ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Deadlocks in WMQI 2.1

Post new topic  Reply to topic
 Deadlocks in WMQI 2.1 « View previous topic :: View next topic » 
Author Message
Nyusser
PostPosted: Wed Nov 27, 2002 3:31 am    Post subject: Deadlocks in WMQI 2.1 Reply with quote

Apprentice

Joined: 02 Jul 2002
Posts: 48

Hi,

I have several message flows which all update the same database table. When these flows are stressed with continuous incoming messages, the processing of some messages fail with the following error message:

SQLSTATE 40001 - [IBM][CLI Driver][DB2/NT]SQL0911N The current transaction has been rolled back because of a deadlock or timeout.

It seems that the update in one flow locks the table and the update in another flow then fails. How do I avoid these deadlocks? I tried to change LOCKTIMEOUT of the database from -1 to 10 seconds, but it didn't make any difference. Any suggestions?

Regs,
Nyusser
Back to top
View user's profile Send private message
vmcgloin
PostPosted: Wed Nov 27, 2002 5:18 am    Post subject: Reply with quote

Knight

Joined: 04 Apr 2002
Posts: 560
Location: Scotland

Quote:
- Database deadlocks with DB2

If you are using DB2 as the broker database, you may experience database deadlocks under stress conditions when running with multiple threads. This will be identified by the WMQI event log message 2322, with SQL State 40001. This is caused by a DB2 feature called "next key locking". If this problem occurs, then next key locking can be disabled by typing db2set DB2_RR_TO_RS=YES in a DB2 command window and restarting the DB2 database manager.
Refer to the DB2 product documentation for more information.


The above is a quote from some notes our team have. I can't remember where it came from though - Problem Determination/Q&A Guide, or FAQs on the IBM site maybe.

Vicky
Back to top
View user's profile Send private message
leongor
PostPosted: Wed Nov 27, 2002 5:51 am    Post subject: Reply with quote

Master

Joined: 13 May 2002
Posts: 264
Location: Israel

Try increasing DB2 LOCKLIST parameter to ~20000.
Also DB2 MAXLOCKS can be increased.
_________________
Regards.
Leonid.

IBM Certified MQSeries Specialist.
Back to top
View user's profile Send private message
Nyusser
PostPosted: Fri Nov 29, 2002 4:36 am    Post subject: Reply with quote

Apprentice

Joined: 02 Jul 2002
Posts: 48

Thanks. I'll try your suggestions.

Regs, Nyusser
Back to top
View user's profile Send private message
mqsidude
PostPosted: Thu Feb 24, 2005 1:56 am    Post subject: Deadlocks in WBI??? Reply with quote

Centurion

Joined: 22 Jan 2004
Posts: 148

Hi folks,

In one of our projects, i see the same problem happening with WBI 5 + DB2 8. This seems to be a problem with DB2 lower versions (< 7). The reponses in this forum point at tuning few DB2 instance parameters although none of posts gave exact solution.

Can anyone of you who have solved this kind of problem post the exact solution?

-Crony
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Deadlocks in WMQI 2.1
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.