| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| configmgr-broker synchronization |
« View previous topic :: View next topic » |
| Author |
Message
|
| jurop |
 Posted: Mon Oct 17, 2005 7:02 am Post subject: configmgr-broker synchronization |
 |
|
Novice
Joined: 17 Oct 2005
Posts: 13
Location: Slovakia
|
I don't know exactly how did we reach the wrong status of our broker/configmgr. The problem is following:
On the AIX broker I can see the EG and MF running on it (mqsilist broker -e EG), but in the toolkit I don't see this EG. Other EGs are seen normally.
Everything is working except I can not remove this EG (and its MF).
How can I synchronize the broker with the configmgr? |
|
| Back to top |
|
 |
| bobbee |
| Posted: Mon Oct 17, 2005 9:41 am Post subject: |
|
|
Knight
Joined: 20 Sep 2001
Posts: 545
Location: Tampa
|
Do you see messages in the Event Viewer, Syslog? Have you tried bouncing the Config and Broker. When you force kill the MF/EG do they restart automatically??
We had this once and support gave us a couple of quick instructions. Unfort......I neglected to write them down. But it is quick and painless if you get them on the phone.
As for what happened. You (or someone) removed the EG/MF from the configuration and the message never go to the Broker and was lost. Good reason NOT to let everyone do deploys!!!! The Config Mgr removes it and relies on MQ to deliver the msg to the broker.
bobbee |
|
| Back to top |
|
|
| jurop |
| Posted: Mon Oct 17, 2005 11:27 pm Post subject: |
|
|
Novice
Joined: 17 Oct 2005
Posts: 13
Location: Slovakia
|
There are no messages in the event viewer/syslog. The situation persists also after restart of configmgr/broker.
When I tried to kill the EG, the broker started it again.
When it happened the last time we were advised to remove the EG directly from the brokers's databaze,
which I don't like very much ... but it seems there is no other way. |
|
| Back to top |
|
|
| bobbee |
| Posted: Tue Oct 18, 2005 4:38 am Post subject: |
|
|
Knight
Joined: 20 Sep 2001
Posts: 545
Location: Tampa
|
That is what we did the last time we had this problem. I
notice that WBI programmers will interact with the broker simular to the way everyone uses a Windows GUI, click, click, click and double click.
This tends to fry the config mgr and brokers brain. At least from experience. With assured delivery, one click equates to one message that "SHOULD" not get lost. If they did not get an answer back the SOMETHING is wrong in the messaging transport (9 times out of ten). Given the way some systems are put together bouncing and mucking around with the queue managers and the WBI services will cause these kinds of situations.
Was this DEV or something higher. If it is not DEV only one person should be doing the deploys. Probably you. It will make your life calmer.
bobbee |
|
| 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
|
|
|
|
