| Author |
Message
|
| senMQ |
 Posted: Fri Jun 06, 2008 12:08 pm Post subject: Deleting execution group |
 |
|
Acolyte
Joined: 14 Aug 2006
Posts: 66
Location: Palo Alto, CA
|
We have a number of EGs running on Msg. Broker v5 environment. We are in the process of retiring this version of Broker. An execution group process shows as if it is running even after I deleted a EG using tool kit. Broker restart didnt do the trick. The EG (which is supposed to be non-existent) starts up. But, I dont see this in tool kit. So, I'm struck now. How do i remove this out of the broker once and for all.
Thanks |
|
| Back to top |
|
 |
| sri_csee1983 |
| Posted: Sat Jun 07, 2008 8:31 am Post subject: |
|
|
Centurion
Joined: 25 Mar 2008
Posts: 125
Location: Chennai,India
|
Did u check after deleting the broker using mqsideletebroker? (only if u r recreating fully)
_________________
With Cheers,
Sri |
|
| Back to top |
|
|
| senMQ |
| Posted: Sat Jun 07, 2008 11:27 am Post subject: |
|
|
Acolyte
Joined: 14 Aug 2006
Posts: 66
Location: Palo Alto, CA
|
My question was about deleting Execution Group and not the broker itself. Pls read the question fully.
Thanks |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Jun 07, 2008 6:41 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Well as the broker is involved in pub/sub (even if you only consider its status messages) there is always at least one execution group running...
This can be the "default" group or some "SYSTEM" eg. ($SYS...)
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| senMQ |
| Posted: Sun Jun 08, 2008 2:33 pm Post subject: |
|
|
Acolyte
Joined: 14 Aug 2006
Posts: 66
Location: Palo Alto, CA
|
| There are at least 3 EGs (apart from default) left after the deletion of the concerned EG. |
|
| Back to top |
|
|
| sri_csee1983 |
| Posted: Sun Jun 08, 2008 5:57 pm Post subject: |
|
|
Centurion
Joined: 25 Mar 2008
Posts: 125
Location: Chennai,India
|
As fjp_saper told, there is no broker without an EG. So it is not possible to delete all the EGs.
I thought u r going to delete all the EGs and recreate them for this retiring process. After deleting all ur EGs what else u have ur broker to run for? Its k. Its upto u to decide.
After deleting the EG, is that listing with the command mqsilist <broker name>. If still listing did u try with the command
mqsideleteexecutiongroup -i host -p 1414 -q QMGR -b BROKER –e EG1
where
host
Is the host name or IP address of the Configuration Manager for the domain on which the broker resides.
1414
Is the port on which the Configuration Manager's queue manager is listening.
QMGR
Is the name of the Configuration Manager's queue manager.
BROKER
Is the name of the broker.
EG1
Is the name of the execution group that you want to delete.
On completion of this task, the execution group is no longer running on the specified broker. In addition, any message flows that were running on the execution group are no longer running.
_________________
With Cheers,
Sri |
|
| Back to top |
|
|
| senMQ |
| Posted: Mon Jun 09, 2008 7:35 am Post subject: |
|
|
Acolyte
Joined: 14 Aug 2006
Posts: 66
Location: Palo Alto, CA
|
Where do I run this command from? broker server or Config manager server?
I'm not able to find the executable in either servers. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Mon Jun 09, 2008 9:16 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Ah, this command was added in v6.0 - it won't be there in your v5 environment.
Removing the EG from the toolkit is the only option. Raise a PMR if you're having difficulties getting permanently rid of it.
Bear in mind that you can't get rid of every execution group (one is always required for pubsub). |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Jun 09, 2008 10:01 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I think it's going to be difficult for senMQ to raise a PMR for v5, mqmatt...
I think it may help to search for 'phantom execution group'...
or recreate the whole broker, and redeploy only the things one needs.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Jun 09, 2008 10:48 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
WB-IMB is supported by IBM until September 30th of this year.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Jun 09, 2008 12:42 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| PeterPotkay wrote: |
| WB-IMB is supported by IBM until September 30th of this year. |
Is it still 2008? Oh, I guess so.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| sri_csee1983 |
| Posted: Mon Jun 09, 2008 6:15 pm Post subject: |
|
|
Centurion
Joined: 25 Mar 2008
Posts: 125
Location: Chennai,India
|
Well Well its going to be interesting and a good experience for SenMQ.
Ok, u can find the mqsilist in the broker installed server. But as Mqmatt told execution group command is in V6 and not in V5. Did u check the connectivity between the ConfigMgr QM and Ur Broker QM?
Because this happend for me once, the connection between the ConfigMgr QM and Broker QM was broken, without knowing that I right clicked and deleted the EG in the toolkit, the EG then was not found in the toolkit but it was there in broker, only reason what I found was there was Queue Depth in the transmission queue (with the name of broker QM). Since I found this after a long time, no other go for me at that time, I deleted and recreated the entire broker and added again.
Before that one thing u can try out. Check for the connectivity between the CM QM and Broker QM and then if it is OK, try deleting the broker in ur ToolKit and then again add the broker. This has a less chance to work, provided the deletion of broker in tool kit clears all of the database entries pertaining to ur broker. If this works carry out. If is throws the error, post the entire error log that is present in the Event Viewer log.(It may through the UUID for the broker does not match error, we may try for that also.)
Or else AFAIK u have to delete the broker with the cmd mqsideletebroker and create again (mqsicreatebroker) and the again add it to the tool kit and create ur EGs and deploy the flows.
_________________
With Cheers,
Sri |
|
| Back to top |
|
|
| servi |
| Posted: Fri Jul 18, 2008 2:38 am Post subject: |
|
|
Novice
Joined: 19 Mar 2008
Posts: 22
Location: Madrid, España
|
Try this:
1.Stop the Broker
2. Connect to Broker DB and set ProcessState=3 and DynamicState=3 for the Phantom EG.
3 Restart the Broker and show the number of EG displayed in the Toolkit are the same that shows mqsilist.
Good luck |
|
| Back to top |
|
|
|
|
