MQSeries.net :: View topic - Messages on CONFIG.QUEUE

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Messages on CONFIG.QUEUE

Messages on CONFIG.QUEUE

« View previous topic :: View next topic »

Author

Message

TCV

Posted: Thu Aug 21, 2003 7:10 am Post subject: Messages on CONFIG.QUEUE

Apprentice

Joined: 21 Aug 2003
Posts: 48

Hi,
I am trying to connect to the configmgr from the controlcenter.The controlcenter window opens.But if i try to do some thing it Generates a BIP1350E and says the Operation is timed out. I see all messages on the queue SYSTEM.BROKER.CONFIG.QUEUE pilingup.I have all the configurations done.

Thanks
TC Venkatesan

mpuetz

Posted: Thu Aug 21, 2003 9:10 am Post subject:

Centurion

Joined: 05 Jul 2001
Posts: 149
Location: IBM/Central WebSphere Services

Hi,

if messages keep sitting on the control queue that means on of the following:

1) Your broker is not running

If you are sure you started it, check that it at least got that
far, that it opened the control queue by looking at *open input count*
parameter of the SYSTEM.BROKER.CONTROL.QUEUE which should be 1
(you can do that using the MQ explorer or the runmqsc command line
tool using DIS QL(SYSTEM.BROKER.CONTROL.QUEUE).

2) If your broker is running check the log file of the broker and see
if there are any entries which tell you why its not processing any
control messages.
Also check the first message on the control queue and see if its
backout count is larger than 0 (using the MQ Explorer by double
clicking on the message)

3) If the backout count is 0 and open input count is 1. Please re-check
the spelling of your broker name in the topology domain. That could
be the reason why the broker "isn't interested" in the control messages.
If everything looks normal a good check to see if your broker is
reacting properly to external requests is to shut it down using
mqsistop BROKER without any additional options. If it doesn't
shut down in a timely manner that usually indicates something
more seriously is wrong with your setup.

If any of this doesn't help try to collect more information (system logs,
mq error logs, db2 diaglogs etc.) and re-post them here or (which is the recommended way in this situation call your IBM support to guide you through the analysis step-by-step.
_________________
Mathias Puetz

IBM/Central WebSphere Services
WebSphere Business Integration Specialist

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Messages on CONFIG.QUEUE

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