| Author |
Message
|
| bdrummond |
 Posted: Wed Feb 16, 2005 12:54 am Post subject: Duplicate Execution Groups (v5) |
 |
|
Disciple
Joined: 06 May 2004
Posts: 164
|
Hi,
I seem to have deployed the same execution group twice where 1 copy appears in the toolkit yet 2 appear on the broker.
If I delete the execution group from the toolkit, 1 'copy' of the execution group remains on the broker.
Does anyone know how to refresh the broker (ie, delete the remaining instance of the excution Group)...?
Cheers. |
|
| Back to top |
|
 |
| lillo |
| Posted: Wed Feb 16, 2005 12:58 am Post subject: |
|
|
Master
Joined: 11 Sep 2001
Posts: 224
|
We also found that problem when playing with an EG and got to a fuzzy state. The only way we could solve it was recreating the EG.
BRs
_________________
Lillo
IBM Certified Specialist - WebSphere MQ |
|
| Back to top |
|
|
| bdrummond |
| Posted: Wed Feb 16, 2005 1:02 am Post subject: |
|
|
Disciple
Joined: 06 May 2004
Posts: 164
|
Hi,
I have deleted the EG from the toolkit and have redeployed the Broker Topology. However, the EG still remained on the broker.
I recreated the EG in the toolkit and redeployed yet I still have the 2 instances on the broker. (???) |
|
| Back to top |
|
|
| lillo |
| Posted: Wed Feb 16, 2005 1:12 am Post subject: |
|
|
Master
Joined: 11 Sep 2001
Posts: 224
|
You have to delete the broker and create it again. Remember to remove the broker from the topology before delete it.
BRs
_________________
Lillo
IBM Certified Specialist - WebSphere MQ |
|
| Back to top |
|
|
| bdrummond |
| Posted: Wed Feb 16, 2005 1:22 am Post subject: |
|
|
Disciple
Joined: 06 May 2004
Posts: 164
|
D'oh. I thought that might be the case but I was hoping there was a way around it.
Thanks for your help. |
|
| Back to top |
|
|
| Andi.MQ |
| Posted: Wed Feb 16, 2005 3:53 am Post subject: |
|
|
Novice
Joined: 10 Dec 2003
Posts: 11
Location: Switzerland
|
Hello
We had the same problem on a V5 Broker on z/OS. We solved it as follows:
- complete deploy of the topology
- stop the broker with the mqsistop command or P <Broker> on z/OS
- kill the reamainig execution group but not the brokerprocess (the brokerprocess then stopps automatically)
- start the broker
This was working for us.
Regards,
Andi. |
|
| Back to top |
|
|
| Heidi-Lize |
| Posted: Wed Feb 16, 2005 10:20 pm Post subject: |
|
|
Newbie
Joined: 20 Jan 2005
Posts: 6
Location: South Africa
|
Hi Guys
We had the same problem in our development environment running on Windows. Did the following:
-Complete the deploy
-Close WBI
-Stop the IBM MQSeries Broker through Services or command prompt
-Stop the IBM MQSeries Broker ConfigMgr through Services or command prompt (Don't know if it's necessary to do both...)
-In windows task manager kill any remaining DataflowEngine.exe instances (these should however dissapear once you've stop the services)
You can try just killing it through task manager without stopping the service but I tried that and it didn't seem to work...
Hope it helps
Cheers! |
|
| Back to top |
|
|
|
|
