| Author |
Message
|
| emileke |
 Posted: Fri Jul 29, 2005 3:14 am Post subject: ORPHANED EXECUTION GROUP IN BROKER AFTER DELETE EG ISSUED |
 |
|
Centurion
Joined: 19 Aug 2001
Posts: 110
Location: South Africa
|
http://www-1.ibm.com/support/docview.wss?uid=swg1IC42230
In the above document, reference is made to # "The orphaned EG can not be removed unless a "Removed All Deployed" command is issued from the Toolkit#
Can somebody please tell me where in the toolkit I have to execute this ? |
|
| Back to top |
|
 |
| JT |
| Posted: Fri Jul 29, 2005 6:25 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Quote: |
To remove the deployed children from a broker:
- Switch to the Broker Administration perspective.
- In the Domains view, expand the broker domain to reveal the execution group with which you want to work.
- Right-click the execution group, and click Remove Deployed Children.
- Click OK at the prompt to confirm that you want to remove all message flows and message sets from the execution group.
An automatic broker configuration deploy is immediately performed for the broker parent. |
|
|
| Back to top |
|
|
| emileke |
| Posted: Sun Jul 31, 2005 10:00 pm Post subject: |
|
|
Centurion
Joined: 19 Aug 2001
Posts: 110
Location: South Africa
|
| thanks, have done this but still has a orphoned execution group. Will try after installing CSD05 |
|
| Back to top |
|
|
| TonyD |
| Posted: Mon Aug 01, 2005 7:45 pm Post subject: |
|
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
Here is an approach that was worked out by a frustrated (by zombie egs) colleague of mine:
1. Go to the broker database
2. Locate BROKERAAEG table
3. Delete the row where PROCESSID = the Windows processid under Task
Manager
4. Do deploy Topology Configuration -> complete
5. MQSISTOP broker
6. MQSISTART broker
7. MQSILIST broker. The execution group should disappear
8. Count the number of Dataflowengines in Task Manager
9. Count the number of execution groups in WBIMB
10. If 8. and 9. are the same, it works !
11. Otherwise, find another medieval method.
Since it involves accessing one of the Broker tables directly, albeit in a minor way, you use at your own risk! |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Aug 01, 2005 8:40 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| emileke wrote: |
| thanks, have done this but still has a orphoned execution group. Will try after installing CSD05 |
Now that you've deleted all the dependants have you tried and deleted the EG again ?
Are you sure there are no flows in error that need intervention and prevent you from removing all the flows deployed to the EG ?
Enjoy  |
|
| Back to top |
|
|
| emileke |
| Posted: Mon Aug 01, 2005 11:53 pm Post subject: Orphoned EG - Solved |
|
|
Centurion
Joined: 19 Aug 2001
Posts: 110
Location: South Africa
|
1. Go to the broker database
2. Locate BROKERAAEG table
3. Delete the row where PROCESSID = the Windows processid under Task
Manager
4. Do deploy Topology Configuration -> complete
5. MQSISTOP broker
6. MQSISTART broker
7. MQSILIST broker. The execution group should disappear
8. Count the number of Dataflowengines in Task Manager
9. Count the number of execution groups in WBIMB
10. If 8. and 9. are the same, it works !
11. Otherwise, find another medieval method.
The above did the trick for me.
Problem solved
Thanks
Emile
_________________
Emile M Kearns |
|
| Back to top |
|
|
| damianharvey |
| Posted: Wed Sep 14, 2005 2:24 pm Post subject: |
|
|
Acolyte
Joined: 05 Aug 2003
Posts: 59
Location: Sydney, Australia
|
The above also worked for me however not until I rebooted my Server (RedHat Linux ES 3.0 running CSD05).
MQSILIST and /var/log/messages were reporting processes that did not exist on the system.
I think that the fix implemented in CSD05 (IC42230) is inadequate. Doing a refresh should reload the topology based on the reality of the broker. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Fri Sep 16, 2005 5:51 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Note that if you delete an execution group that is being used for pubsub, it will not be removed until the broker is next restarted.
All brokers need one execution group for this, in order to enable communication with the Config Manager.
You can find out which execution group is being used for pubsub by looking at the 'execution group started' message in the system event log (BIP2201) - look for "defaultExecutionGroup 'true'", which means that any deletion of this execution group will not really occur until the next broker restart.
-Matt |
|
| Back to top |
|
|
| Tibor |
| Posted: Tue Oct 25, 2005 2:19 pm Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
| mqmatt wrote: |
Note that if you delete an execution group that is being used for pubsub, it will not be removed until the broker is next restarted.
All brokers need one execution group for this, in order to enable communication with the Config Manager.
You can find out which execution group is being used for pubsub by looking at the 'execution group started' message in the system event log (BIP2201) - look for "defaultExecutionGroup 'true'", which means that any deletion of this execution group will not really occur until the next broker restart. |
Thank you the answer, Matt, what I'm looking for a while  There was an earlier topic but nobody knows this property.
And how can I tight this function to a wanted execution group?
Tibor |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Oct 25, 2005 3:36 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| Tibor wrote: |
| And how can I tight this function to a wanted execution group? |
At a first pass, I'd guess delete all the execution groups OTHER than the one you want, restart the broker, create new execution groups, redeploy...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Tibor |
| Posted: Wed Oct 26, 2005 12:01 am Post subject: |
|
|
Grand Master
Joined: 20 May 2001
Posts: 1033
Location: Hungary
|
Jeff,
I like your idea  but this is not working! As far as I observed the last created EG is the default pubsub.
Tibor |
|
| Back to top |
|
|
|
|
