| Author |
Message
|
| EnOne |
 Posted: Fri Jan 07, 2005 6:23 am Post subject: Message flows not showing in V5 AIX |
 |
|
Centurion
Joined: 09 Oct 2002
Posts: 100
Location: Kansas City
|
I seem to keep on having a peculiar problem with V5 on AIX. Occasionaly a message flow will be deployed to an execution group but it does not show under Domains in the Broker Administration Perspective. I can still see it using the mqsilist -e command and if I deploy the same message flow to the same execution group a second instance of the same message flow appears.
Is there a way to remove a single message flow from an execution group using the command line in AIX? How do you remove a message flow from an execution group if the message flow does not show in the Broker Administration Perspective? (other than rebuilding the execution group)[/b] |
|
| Back to top |
|
 |
| chenulu |
| Posted: Fri Jan 07, 2005 9:24 am Post subject: |
|
|
Voyager
Joined: 27 Mar 2002
Posts: 87
Location: Research Triangle Park, NC
|
Hi,
Try doing a complete deploy to the broker to see if the CMGR syncs up with the broker
-- Chenulu |
|
| Back to top |
|
|
| PGoodhart |
| Posted: Fri Jan 07, 2005 11:22 am Post subject: |
|
|
Master
Joined: 17 Jun 2004
Posts: 278
Location: Harrisburg PA
|
You may have a "rogue execution group". Try searching for that on the support site, there are instructions on how to fix it.
_________________
Patrick Goodhart
MQ Admin/Web Developer/Consultant
WebSphere Application Server Admin |
|
| Back to top |
|
|
| EnOne |
| Posted: Fri Jan 07, 2005 12:32 pm Post subject: |
|
|
Centurion
Joined: 09 Oct 2002
Posts: 100
Location: Kansas City
|
I found this on the IBM support site about rogue execution groups it is what I was seeing
http://www-1.ibm.com/support/docview.wss?uid=swg21171291
we did this to remove the old execution group then it was rebuilt. It would be nice to have more control of the execution groups and the messages within them from the command line. |
|
| Back to top |
|
|
| rkford11 |
| Posted: Fri Jan 07, 2005 1:01 pm Post subject: |
|
|
Partisan
Joined: 06 Jun 2004
Posts: 316
|
| njpeeke wrote: |
I found this on the IBM support site about rogue execution groups it is what I was seeing
http://www-1.ibm.com/support/docview.wss?uid=swg21171291
we did this to remove the old execution group then it was rebuilt. It would be nice to have more control of the execution groups and the messages within them from the command line. |
What do you mean by rogue execution groups?
Are they the one which does not execute message flows.please give me some more information on this.
Thanks |
|
| Back to top |
|
|
| EnOne |
| Posted: Fri Jan 07, 2005 2:25 pm Post subject: |
|
|
Centurion
Joined: 09 Oct 2002
Posts: 100
Location: Kansas City
|
rogue execution group: an execution group that refuses to allow a message flow to be removed from it.
It's not that it won't process message flows but that it won't stop processing message flows. The message flow will be shown as removed from the Domains window within the Broker Administration Perspective but the message flow will still process messages. The only way to see the message flow is to run mqsilist [broker] -e [rogue execution group] this will allow you to see the message flow but it will not give you the ability to remove it.
Does this clarify? |
|
| Back to top |
|
|
| rkford11 |
| Posted: Fri Jan 07, 2005 3:16 pm Post subject: |
|
|
Partisan
Joined: 06 Jun 2004
Posts: 316
|
| njpeeke wrote: |
rogue execution group: an execution group that refuses to allow a message flow to be removed from it.
It's not that it won't process message flows but that it won't stop processing message flows. The message flow will be shown as removed from the Domains window within the Broker Administration Perspective but the message flow will still process messages. The only way to see the message flow is to run mqsilist [broker] -e [rogue execution group] this will allow you to see the message flow but it will not give you the ability to remove it.
Does this clarify? |
Thanks njpeeke. your reply clarifies all my doubts. |
|
| Back to top |
|
|
| sorn73 |
| Posted: Thu Nov 03, 2005 8:43 am Post subject: |
|
|
Novice
Joined: 24 Mar 2004
Posts: 24
Location: Sweden
|
| I also have this roblem with rogue flows/execution groups, where I can see multiple instances of a flow, but I can only remove one instance. And the duplicates continue to process message. However, I'm not at liberty to remove the entire execution group, as this is a production environemt. Is there any may to remove a rogue flow without deleting the entire execution group? |
|
| Back to top |
|
|
| EnOne |
| Posted: Thu Nov 03, 2005 9:29 am Post subject: |
|
|
Centurion
Joined: 09 Oct 2002
Posts: 100
Location: Kansas City
|
Currently, No. 
We use the mqsilist function to perodically check our execution groups but other than deleting the entire execution group then rebuilding it and redeploying all of the message flows we are yet to find a way to fix this.
We use dual execution groups in production for just this purpose so we do not have an outage during deploys or rebuilding.
It would be nice to have a command line interface that would remove a single message flow from an execution group but it does not exist yet. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Nov 03, 2005 9:38 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| njpeeke wrote: |
| It would be nice to have a command line interface that would remove a single message flow from an execution group but it does not exist yet. |
I think the Config Mgr Proxy API in v6 lets you do this.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu Nov 03, 2005 9:46 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| jefflowrey wrote: |
| njpeeke wrote: |
| It would be nice to have a command line interface that would remove a single message flow from an execution group but it does not exist yet. |
I think the Config Mgr Proxy API in v6 lets you do this. |
mqsideploy ... -d flowname1:flowname2 .... 
_________________
-wayne |
|
| Back to top |
|
|
| EnOne |
| Posted: Thu Nov 03, 2005 10:39 am Post subject: |
|
|
Centurion
Joined: 09 Oct 2002
Posts: 100
Location: Kansas City
|
| We're still on V5 but it's nice to know that there is a fix in V6 when we eventually upgrade. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Thu Nov 03, 2005 11:49 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
Couldn't you use the -rm* flags on the v5 mqsideploy command?
| Quote: |
-rmMsgFlow msgFlowName' remove specified deployed message flow.
-rmMsgSet msgSetName' remove specified deployed message set.
|
|
|
| Back to top |
|
|
| pganpath |
| Posted: Wed Feb 14, 2007 6:46 am Post subject: Message flow showing in AIX even when deleted from Toolkit |
|
|
Newbie
Joined: 14 Feb 2007
Posts: 1
Location: Ann Arbor
|
I am having the same problem as below. Has any one found a cure?? Help appreciated!
--------------
I seem to keep on having a peculiar problem with V5 on AIX. Occasionaly a message flow will be deployed to an execution group but it does not show under Domains in the Broker Administration Perspective. I can still see it using the mqsilist -e command and if I deploy the same message flow to the same execution group a second instance of the same message flow appears.
Is there a way to remove a single message flow from an execution group using the command line in AIX? How do you remove a message flow from an execution group if the message flow does not show in the Broker Administration Perspective? (other than rebuilding the execution group)[/b] |
|
| Back to top |
|
|
| mqmatt |
| Posted: Wed Feb 14, 2007 7:39 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
To remove flows from the commandline in v5, you should usually use mqsideploy -rmMsgFlow - but this only works on Windows. On V6 you can use mqsideploy -d or a Config Manager Proxy application.
If you get a phantom message flow appearing in the runtime that is not reflected in the toolkit, you need to use the 'Remove deployed children' option on the execution group, or (again) use the Config Manager Proxy. |
|
| Back to top |
|
|
|
|
