| Author |
Message
|
| KPJones |
 Posted: Wed Sep 22, 2004 10:51 am Post subject: false "Broker is not running" alert |
 |
|
Newbie
Joined: 22 Sep 2004
Posts: 6
Location: 922 Walnut, Kansas City, MO
|
I am getting what I thik is a false "Broker is not running" alert. WBIMB is v5.0.3, MQ is v5.3. I have two brokers on AIX. One broker gives the "Broker is not running" alert even though all AIX processes are running, and a test flow has it's input queue open. Removing the alert works, but refreshing the broker in the toolkit will cause it to pop back up.
Anyone know what is going on?
Thanks, Ken |
|
| Back to top |
|
 |
| mq_pm |
| Posted: Wed Sep 22, 2004 11:26 am Post subject: |
|
|
Centurion
Joined: 27 Aug 2003
Posts: 132
|
what u were trying to do ???
I got this error when i was initially trying to add broker to the topology.
This is due to no communication between configmgr and broker since configmgr and broker had separate Queuemanagers. check whether ur brokers and configmgr have communication links. I am not sure whether this is helpful ..... |
|
| Back to top |
|
|
| KPJones |
| Posted: Wed Sep 22, 2004 11:39 am Post subject: |
|
|
Newbie
Joined: 22 Sep 2004
Posts: 6
Location: 922 Walnut, Kansas City, MO
|
| Sorry - The broker was successfully added to the topology. Broker messages on the AIX log appear normal. As previously stated, a deployed test flow opens it's input queue, indicating that the config. manager is communicating with the broker. BUT still the ugly "Broker is not running" alert! Weird! Oh, I guess I should mention that disconnecting from the config mgr. stopping, rebooting and restarting toolkit and reconnecting to config mgr. does not help. |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Sep 22, 2004 12:23 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| The broker was successfully added to the topology. |
After adding it in your topology in the toolkit did you deploy it to the broker
If you did, then did you get a positive event log message saying so?
| Quote: |
| Removing the alert works, |
What do you mean.
Can you deploy a test message flow after removing the alert? Can you start/stop message flows ? |
|
| Back to top |
|
|
| waugh |
| Posted: Thu Sep 23, 2004 5:04 am Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 225
|
are you sure the broker is running? mqsistart <broker name>
do you see bipbroker process running if you do a grep? |
|
| Back to top |
|
|
| KPJones |
| Posted: Thu Sep 23, 2004 6:08 am Post subject: |
|
|
Newbie
Joined: 22 Sep 2004
Posts: 6
Location: 922 Walnut, Kansas City, MO
|
Hi Vanella, maybe you have hit on the problem. I did not know that after adding the new broker to the topology that one had to deploy the broker to itself! I'll talk to the folks that used to do the Integration and see how that is done. I may be an old salt to MQ, but I'm a newbie to WBIMB.
Everything else is O.K. I know the 4 processes on AIX and everything is up. (I use "ps -ef|grep BROKERNAME". Gets 'em every time.) Yes, positive messages in the event log of the config mgr, and the AIX log also. The fact that the flows run should indicate that processes are up, and the broker is not "mostly dead". I don't know what triggers this alert, but it is persistent. If the broker deployment does not pan out, I am going to write an ETR to IBMLINK. I have been assuming that I did something to cause this, but maybe I really have a bug. Thanks for the advice. Ken |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Sep 23, 2004 6:15 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It's not exactly "deploying the broker to itself". It's really deploying the configuration manager to the broker - i.e. registering the broker with the particular configuration manager.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| KPJones |
| Posted: Thu Sep 23, 2004 11:17 am Post subject: |
|
|
Newbie
Joined: 22 Sep 2004
Posts: 6
Location: 922 Walnut, Kansas City, MO
|
| Dear Jeff & Vanella - I think you may have it, however the silly manuals won't tell me how to register the config mgr. with the new broker. Is it a "drag & drop" like deploying a flow or a line command? (the "mqsiregisterconfigmgr BROKERNAME" command sounds good. But it does not seem to exist. Why do they have to make this stuff so counter-intuitive? Oh, job security... |
|
| Back to top |
|
|
| KPJones |
| Posted: Thu Sep 23, 2004 11:19 am Post subject: |
|
|
Newbie
Joined: 22 Sep 2004
Posts: 6
Location: 922 Walnut, Kansas City, MO
|
| Venella - I am very sorry for getting your name wrong. Guess I am just on a real "winning" streak. Sincere Apologies, Ken |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Sep 23, 2004 11:58 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Okay. Suppose you have just finished running 'mqsicreatebroker'.
The next steps you need to do, in order, and this is in the documentation I'm sure, are - Create channels between the broker queue manager and the configuration queue manager, if this isn't already done and they don't share a queue manager
- Open up the tooling, and switch to the Broker Administration perspective
- Create a domain to establish a connection to the config manager (if this hasn't already been done)
- Connect to the domain.
- Right-click on Broker Topology, and choose New->Broker
- Provide the necessary information to locate your broker
- Right Click on Broker Topology and choose "Deploy Topology Configuration" and either choose Delta or Complete
- Click OK on any windows that pop up, unless they are reporting errors (in which case, click on DETAILS and copy the information down)
- Double-Click on Event Log to open up the event log to confirm that the deploy succeeded.
You can skip any steps that you have already performed.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Nizam |
| Posted: Thu Sep 23, 2004 4:52 pm Post subject: |
|
|
Disciple
Joined: 10 Feb 2004
Posts: 160
|
My personal experience..
My broker and configuration manager are running on different queue managers. I start the broker and configuration manager and still find the alert "broker is not running".
Well the reason was, the channels between queue manager and configuration manager are not running.
KPJones, i feel you should check the channels. |
|
| Back to top |
|
|
| KPJones |
| Posted: Fri Sep 24, 2004 6:48 am Post subject: |
|
|
Newbie
Joined: 22 Sep 2004
Posts: 6
Location: 922 Walnut, Kansas City, MO
|
When I deployed my broker topology, (something that I had done prior to this strange error showing up) I got a "BIP1536S: Configuration Manager unable to register..." followed by "BIP2087E: Broker WBIBUXQ1 was unable to process the internal configuration message..." the key was in the last message, a "BIP2062E: Broker WBIBUXQ1 (UUID 394d60e9-fe00-0000-0080-a02600804d21) Execution Group '' (UUID 044e60e9-fe00-0000-0080-a02600804d21) detected that the deployed configuration message received contained an invalid XML tag..." The message concludes with " Use the Message Brokers Toolkit to redeploy to the Execution Group." So I cleaned up some iffy flows (class projects...) and redeployed. ERROR MESSAGE GONE! And refreshing topology did not cause it to come back! Thanks to Jeff and all for the help. Ken
Vennela - Hey, I think I finally got it right. It is a very nice name - I must have had some kind of block. Thanks for the help. Maybe we will meet at a Tech Conference and I can apologize in person. Ken |
|
| Back to top |
|
|
|
|
