|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
mqsistop, mqsilist, mqsideletebroker all hang there |
« View previous topic :: View next topic » |
Author |
Message
|
chargie |
Posted: Wed Sep 27, 2006 2:04 am Post subject: mqsistop, mqsilist, mqsideletebroker all hang there |
|
|
Novice
Joined: 21 Sep 2006 Posts: 10
|
when I try to run mqsistop against a broker, it just hang there, and couldn't find any valuable info from log. mqsilist and mqsideletebroker have same problem.
I don't know from when the broker is working abnormally, from then on, I found deployment configuration messages and corresponding replies are always blocked in SYSTEM.BROKER.**** queues. even if I clear them, next time when I start broker, not yet deploy any message flow, these queues are again filled in, kind of weird.
I suspect that broker db has some data representing broker's status, I've check those tables one bye one, but couldn't spot on right table by trunscating which I can remove broker db data.
I've encountered this problem for a couple of times, in the past I just started from the beginning, created all again...
this time, I really want to know how to rollback the status to healthy status...
Has anyone had similar experience before? |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Sep 27, 2006 4:50 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
if mqsistop doesn't finish, then the broker is not responding.
You can kill the bip processes. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Sep 27, 2006 4:08 pm Post subject: Re: mqsistop, mqsilist, mqsideletebroker all hang there |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
chargie wrote: |
when I try to run mqsistop against a broker, it just hang there, and couldn't find any valuable info from log. mqsilist and mqsideletebroker have same problem.
I don't know from when the broker is working abnormally, from then on, I found deployment configuration messages and corresponding replies are always blocked in SYSTEM.BROKER.**** queues. even if I clear them, next time when I start broker, not yet deploy any message flow, these queues are again filled in, kind of weird.
I suspect that broker db has some data representing broker's status, I've check those tables one bye one, but couldn't spot on right table by trunscating which I can remove broker db data.
I've encountered this problem for a couple of times, in the past I just started from the beginning, created all again...
this time, I really want to know how to rollback the status to healthy status...
Has anyone had similar experience before? |
Well you did not specify your level.
I usually go and get the sub processes of the bip process (DataFlow....) and kill them one by one.
You may see that after you kill the one that was "hanging" the shutdown process continues on its own.
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
chargie |
Posted: Wed Sep 27, 2006 11:05 pm Post subject: what if it's out of sync between cfg manager and broker |
|
|
Novice
Joined: 21 Sep 2006 Posts: 10
|
This morning, I reboot system without stop configuration manager and broker, then I manaually started database, configuration manager and broker, from toolkit I see all components are running, but when I try to deploy a new bar, I noticed the message is blocked in SYSTEM.BROKER.ADMIN.QUEUE. Is this because the channel SYSTEM.BKR.CONFIG is not up? If yes, why after I started this channel, cancle deployment and re-deploy, message is still blocked in SYSTEM.BROKER.ADMIN.QUEUE. I saw there are some ohter queues also not empty:
SYSTEM.CHANNEL.SYNCQ
SYSTEM.CLUSTER.REPOSITORY
SYSTEM.ADMIN.QMGR.EVENT
SYSTEM.AUTH.DATA.QUEUE
Is there a comman way to make cfg manager and broker sync again, if it's the problem of out-of-sync? |
|
Back to top |
|
 |
fjb_saper |
Posted: Thu Sep 28, 2006 2:53 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Make sure all channels are running fine. Restart the broker. If it still does not consume the messages from the SYSTEM.BROKER.CONTROL.QUEUE you likely hava a poison message in that queue. Backup the first message in that queue and delete it. Restart the broker. Check that it is consuming the queue.
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
jefflowrey |
Posted: Thu Sep 28, 2006 4:02 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Cancel deployment doesn't do what you think it does.
It should really be renamed "Clear broker deploying flag", or something else.
SYSTEM.BKR.CONFIG is used by the Toolkit to connect to the ConfigMgr. It is NOT used by the ConfigMgr to talk to the Broker.
If Broker and ConfigMgr are using different queue managers, then you must establish MQ networking between the two and make sure there is a qmgr alias for ConfigMgr on Broker qmgr and a qmgr alias for Broker on ConfigMgr qmgr.
If Broker is not consuming deployments, then it's STUCK for some reason. Perhaps there is a flow that goes into an infinite loop. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
chargie |
Posted: Thu Sep 28, 2006 4:34 am Post subject: |
|
|
Novice
Joined: 21 Sep 2006 Posts: 10
|
I created new database, new configuration manager, new broker... then it's working again
my configuration manager and broker share the same queue manager.
I used "ps -A | grep bip" to check processes, I found for the sick broker and configuration manager, they don't have a process called biphttplistener, which my new created healthy configuration and broker do have...
I am wondering why this process is not started automatically when I run mqsistart for configration manager and broker...
is it my problem or product defect? |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
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
|
|
|
|