| Author |
Message
|
| lium |
 Posted: Thu May 20, 2010 8:31 am Post subject: messed up execution group name |
 |
|
Disciple
Joined: 17 Jul 2002
Posts: 184
|
When I loaded my toolkit and connected to the remote configmgr on AIX, found that the execution group was messed up again.
The exec ution group name showned up as DiscoveredEG_840c4750-2801-0000-0080-dd9953f94670, for example. Even if I logged into broker server box and display using mqsilist brokername, it also showed the same context.
The same problem happened last time was about more than one month ago. The solution was deleting the execution group and recreated and redeployed message flows again which I don't want to do that way since it is time consuming even if it is dev box.
Any idea to solve this problem?
Great Thanks in advance, |
|
| Back to top |
|
 |
| bloomy |
| Posted: Thu May 20, 2010 9:31 am Post subject: |
|
|
Acolyte
Joined: 11 Feb 2009
Posts: 61
Location: Bloomington, IL USA
|
Connect to the configmgr from toolkit.
1. Do a right click on the Broker Topology
2. Select Topology Cinguration
3. select Complete.
It works for me when I have similar issues. But I never had issues with mqsilist, it shows the correct EG name when I had these issues.
The other solution would be to recycle the broker and configuration manager, so that the broker and configuration manager would get in sync with each other.
The ultimate solution would be to upgrade to WMB7, which does not have configmgr and believe me it works great.  |
|
| Back to top |
|
|
| lium |
| Posted: Thu May 20, 2010 10:28 am Post subject: |
|
|
Disciple
Joined: 17 Jul 2002
Posts: 184
|
Great Thx, Bloomy
First time, I deployed a complete topology, the message broker's mess dispeared. But the toolkit's mess was still there. So I renamed them and did another complete topology deployment, the problem was solved. |
|
| Back to top |
|
|
| lium |
| Posted: Fri May 21, 2010 8:18 am Post subject: |
|
|
Disciple
Joined: 17 Jul 2002
Posts: 184
|
Today, I loaded up my WMB toolkit, evey execution group was messed up again. I checked the Broker box, the execution group's names are all good.
So still have problem, How can solve this problem thoroughly? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri May 21, 2010 9:48 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It sounds like the ConfigMgr and the broker are having difficulties communicating.
I'd check the logs on both machines for errors that may point you to the issue more. |
|
| Back to top |
|
|
| lium |
| Posted: Fri May 21, 2010 1:38 pm Post subject: |
|
|
Disciple
Joined: 17 Jul 2002
Posts: 184
|
Thansk for reply.
Both Broker and Configmgr shared the same qmgr, so there should be no communication problem. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Mon May 24, 2010 1:10 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
First, make sure you're on the latest fixpack (there was a problem in this area that was fixed in one of the later fixpacks).
If you are up-to-date on service, then raise a PMR; something's clearly not right! |
|
| Back to top |
|
|
|
|
