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 » deadlock or timeout starting brokers

Post new topic  Reply to topic
 deadlock or timeout starting brokers « View previous topic :: View next topic » 
Author Message
vmcgloin
PostPosted: Wed May 29, 2002 7:46 am    Post subject: deadlock or timeout starting brokers Reply with quote

Knight

Joined: 04 Apr 2002
Posts: 560
Location: Scotland

Hi,

I have yet another problem with MQSIv202...

BIP2201I: Execution group started
BIP2203E: An execution group has encountered a problem whilst starting.
BIP2371E: Database statement 'SELECT Status FROM MQSIUID.BNBRCONNECTIONS WHERE BrokerUUID = ? AND NeighbourId = ?' could not be executed.
BIP2321E: Database error: ODBC return code '-1'. :
BIP2322E: Database error: SQL State '40001'; Native Error Code '-911'; Error Text '[IBM][CLI Driver][DB2/6000] SQL0911N The current transaction has been rolled back because of a deadlock or timeout. Reason code "2". SQLSTATE=40001:
BIP2204I: Execution group using process '20052' thread '1' stopped. :
BIP2060E: The broker has detected that the execution group default, process ID 20052, has terminated. :

This occurs when starting up 5 brokers which all use the same broker database (DB2 6.1) on AIX.

- Can anyone point me to what database setting I should alter?
- Alternatively does anyone have the pdf for the 202 version of ih01 as I think the answer may be in there (Q&A or Problem Determination)? (Obsolete problems are removed from the current version.)
Back to top
View user's profile Send private message
kirani
PostPosted: Wed May 29, 2002 6:59 pm    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA

Do you get this error evertime you start brokers? Have you tried starting brokers one at a time? What CSD are you using?
_________________
Kiran


IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries

Back to top
View user's profile Send private message Visit poster's website
vmcgloin
PostPosted: Fri May 31, 2002 12:20 am    Post subject: Reply with quote

Knight

Joined: 04 Apr 2002
Posts: 560
Location: Scotland

Kirani,

We only see this when starting several brokers at once. But when we stop them we do need to stop and start them all at the same time.

We are using 202 with CSD02. db2level is "DB2 v6.1.0.31".

We are not using pub/sub.

I know I have seen this before (with 201 or 202) but cannot find any reference to it anywhere... Looks like yet another PMR.

Vicky
Back to top
View user's profile Send private message
MikeC
PostPosted: Wed Dec 01, 2004 10:58 am    Post subject: Reply with quote

Acolyte

Joined: 30 Jun 2003
Posts: 55
Location: Toronto, Canada

Vicky - I know you posted this problem a while ago, but do you remember what the resolution was? I'm encountering the exact same situation now (with WMQI 2.1). There's nothing helpful on the IBM site and I'm at a loss as to the cause.

Or has anyone else encountered the same error and found a way to deal with it?

Thanks,
-Mike.
_________________
-Mike.
Back to top
View user's profile Send private message AIM Address Yahoo Messenger MSN Messenger
chenulu
PostPosted: Wed Dec 01, 2004 1:07 pm    Post subject: Reply with quote

Voyager

Joined: 27 Mar 2002
Posts: 87
Location: Research Triangle Park, NC

Hi,

Increase the LOCKLISTS parameter on the Broker DB to 1000 and restart the brokers and post the results.

Chenulu
Back to top
View user's profile Send private message Send e-mail
MikeC
PostPosted: Fri Dec 03, 2004 6:45 am    Post subject: Reply with quote

Acolyte

Joined: 30 Jun 2003
Posts: 55
Location: Toronto, Canada

Thanks very much. It looks like that worked. ... Just so I know, what exactly did changing that value do to fix the problem?
_________________
-Mike.
Back to top
View user's profile Send private message AIM Address Yahoo Messenger MSN Messenger
chenulu
PostPosted: Fri Dec 03, 2004 6:06 pm    Post subject: Reply with quote

Voyager

Joined: 27 Mar 2002
Posts: 87
Location: Research Triangle Park, NC

Hi Mike,

The lock list holds the controlling information for all locked objects for applications. Storage is allocated for the database lock list (tables and rows) in sizes of 64 bytes for locked objects and 32 bytes for objects already locked. If the lock list is too small, lock escalation can result. When an application reaches the maximum number of locks allowed and there are no more locks to escalate, it will then use space in the lock list allocated for other applications. When the entire lock list is full, an error occurs.

Which is the value I had you increase.

-- Chenulu
Back to top
View user's profile Send private message Send e-mail
MikeC
PostPosted: Sat Dec 04, 2004 6:20 am    Post subject: Reply with quote

Acolyte

Joined: 30 Jun 2003
Posts: 55
Location: Toronto, Canada

Helpful and informative post. Thanks very much.
_________________
-Mike.
Back to top
View user's profile Send private message AIM Address Yahoo Messenger MSN Messenger
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » deadlock or timeout starting brokers
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.