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 » broker is not running

Post new topic  Reply to topic
 broker is not running « View previous topic :: View next topic » 
Author Message
mahek
PostPosted: Wed Sep 28, 2016 11:14 am    Post subject: broker is not running Reply with quote

Voyager

Joined: 10 Sep 2004
Posts: 87

Hi All,

I have an issue where the MESSAGE BROKER 7.0 is up and running and processing message but when i try to connect to it using toolkit it is telling that the broker is not running. mqsilist BrokerName is also timing out. Any help is appreciated
Back to top
View user's profile Send private message
Craig B
PostPosted: Wed Sep 28, 2016 11:55 am    Post subject: Reply with quote

Partisan

Joined: 18 Jun 2003
Posts: 316
Location: UK

WMB V7 ... you do know that is out of support now?

The Toolkit uses the Integration API to connect to the Brokers queue manager. The first message it will send is a registration message. If it does not get a response within 60 seconds then it assumes the broker is not running. mqsilist is also an Integration API based application but is tied a little bit more to the broker run-time. It can detect the bipbroker process is running and then try and connect in the same way that the Toolkit does. The fact it is hanging suggests that the command thinks the bipbroker process is running but has not got any answer.

On your broker queue manager can you check the depths of the SYSTEM.BROKER.DEPLOY.QUEUE and SYSTEM.BROKER.DEPLOY.REPLY queues to see if there is any build up on these?
_________________
Regards
Craig
Back to top
View user's profile Send private message
mahek
PostPosted: Wed Sep 28, 2016 2:05 pm    Post subject: Reply with quote

Voyager

Joined: 10 Sep 2004
Posts: 87

Thanks a lot for the Reply. The queue depth on this queue is 74800.I am not sure why we have this message on the SYSTEM.BROKER.DEPLOY.QUEUE
Back to top
View user's profile Send private message
Craig B
PostPosted: Wed Sep 28, 2016 8:36 pm    Post subject: Reply with quote

Partisan

Joined: 18 Jun 2003
Posts: 316
Location: UK

What are the IPPROCS/OPPROCS count on the queue? Can you issue the following command and add the output to the thread:

mqsireportproperties brokerName -b agent -o DeployThreadManager -r
_________________
Regards
Craig
Back to top
View user's profile Send private message
mahek
PostPosted: Thu Sep 29, 2016 9:44 am    Post subject: Reply with quote

Voyager

Joined: 10 Sep 2004
Posts: 87

Thanks a lot for your reply. The input IPPROCS=10 OPPROCS =5


D:\IBM\MQSI\7.0>mqsireportproperties MDBKRPB07 -b agent -o DeployThreadManager -r
BIP2037E: The internal configuration message has been discarded.
An internal configuration message could not be processed to completion, even though multiple attempts were made to process the message.
Review any other messages written to the system log to determine the cause of the failure. If you are unable to determine the cause of failure, contact your IBM support center.

BIP8036E: Negative response received.
This command sends an internal configuration message to the broker, the response received indicated that the internal configuration message was unsuccessful.
Check that the WebSphere MQ transport is available. Check the system log for further information.
Back to top
View user's profile Send private message
Craig B
PostPosted: Thu Sep 29, 2016 10:38 am    Post subject: Reply with quote

Partisan

Joined: 18 Jun 2003
Posts: 316
Location: UK

The BIP2037 is issued by the AdminAgent when it thinks the BackoutCount of the request message had exceeded 2. This suggests that a thread is picking up the current request message but backing it out immediately. At a guess it would seem your bipbroker is locked up the few threads that are still processing fail after not being able to acquire resources (such as internal locks) and hence roll back the current message. Do you have any messages in the SYSLOG/EventVwr for the time frame this broker has been in this state?
_________________
Regards
Craig
Back to top
View user's profile Send private message
Tuyenpx
PostPosted: Tue Oct 04, 2016 12:54 am    Post subject: Re: broker is not running Reply with quote

Newbie

Joined: 04 Oct 2016
Posts: 3

mahek wrote:
Hi All,

I have an issue where the MESSAGE BROKER 7.0 is up and running and processing message but when i try to connect to it using toolkit it is telling that the broker is not running. mqsilist BrokerName is also timing out. Any help is appreciated





Please start Message Queue in Service. You can access in it from Start ->Administrative Tools -> Services. Hope that you need
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 » broker is not running
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.