| Author |
Message
|
| alanjhunter |
 Posted: Mon Dec 12, 2005 7:53 am Post subject: Unable to remove message flow from Broker |
 |
|
Newbie
Joined: 07 Oct 2005
Posts: 4
Location: Edinburgh, Scotland
|
I am having a problem with removing a particular message flow from one of our development brokers. Have recently deployed a new version of the flow, which was failing with parser errors.
So, I removed it from the broker via Websphere Studio and the broker view does not show it as being deployed. However, I have an 'Input Count' of 2 against my request queue and an 'mqsilist' list shows the message flow is running twice.
Have ran an 'mqsideploy' with the '-r' option to remove it and it says it has completed and successfully deleted the flow/s. However, another 'mqsilist' list shows it as still running.
Have bounced the Broker, but to no avail.
Has anyone seen a similar problem or can advise a next step ?
Thanks. |
|
| Back to top |
|
 |
| shrek |
| Posted: Mon Dec 12, 2005 8:46 am Post subject: |
|
|
Acolyte
Joined: 19 Feb 2005
Posts: 61
Location: Gudivada,India
|
Are you sure that it is deployed to only one Execution Group? Please ensure and if that was the case. You may want to try stopping the broker and clean the Shared Memory/Semaphores and bring back the broker.
You can also try performing a complete deploy on the Execution Group once the broker is up and running.
Thanks. |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Mon Dec 12, 2005 8:09 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi alanjhunter,
You should try Cancel all deployments, Disconnecting the brokers....Restarting the Config Mgr and Brokers.
Then reconnect and try to deploy or remove again.
I have noticed that many a times the Toolkit says that the command has been executed and pops up the window, but the command is not actually executed, and is pending, mostly due to connectivity.
Regards. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Dec 13, 2005 4:36 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| elvis_gn wrote: |
| I have noticed that many a times the Toolkit says that the command has been executed and pops up the window, but the command is not actually executed, and is pending, mostly due to connectivity. |
Right. That's why you always wait until the Event Log viewer in the Toolkit shows that the broker has actually performed the command, and returned a response to the configmgr.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| alanjhunter |
| Posted: Tue Dec 13, 2005 5:57 am Post subject: |
|
|
Newbie
Joined: 07 Oct 2005
Posts: 4
Location: Edinburgh, Scotland
|
Believe me, the Toolkit DOES come back with a successfull delete.
However, it only deletes the original occurence of the flow. There somehow seems to be 2 copies of the flow still running on the broker, and toolkit shows NONE are running.
The 'mqsdeploy -r' command was run physically on our Unix box and again it comes back with a successfull completion. But the 2 flows still exist, and you can see them via an 'mqsilist' command. |
|
| Back to top |
|
|
| wschutz |
| Posted: Tue Dec 13, 2005 6:00 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
I've seen this, I've just deleted the entire EG and redeployed.
_________________
-wayne |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Dec 13, 2005 6:10 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You say the flow was failling with parsing errors.
I'm going to guess that the flow didn't handle the errors correctly, and has gotten stuck in a loop.
Get disable the input queue. Kill the EG process. Remove the flow entirely, and do a complete deployment.
If that doesn't work, drop and recreate the broker.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| moorej_gl |
| Posted: Tue Dec 13, 2005 2:42 pm Post subject: |
|
|
Apprentice
Joined: 01 Dec 2003
Posts: 35
Location: Madison, WI
|
I saw something kind of similar. I think the broker was at PF05 (v5.0) and the developer's toolkit was only at FP03. Each time he stopped a message flow from his toolkit, an additional instance of the message flow was generated (we knew this by mqsilist & the number of threads open on the input queue; the toolkit showed nothing unusual). When I tried removing it from the EG, the toolkit showed that it had been removed, but mqsilist still showed the additional instances. Only a 'remove all deployed children' would remove the additional threads. Once we realized & corrected the FP discrepancy, undeployed & redeployed everything, did it clear up. Stopping & starting the broker, rebooting the server, etc. had not helped.
It may be a long shot, but worth checking in any case. |
|
| Back to top |
|
|
| alanjhunter |
| Posted: Wed Dec 14, 2005 2:33 am Post subject: |
|
|
Newbie
Joined: 07 Oct 2005
Posts: 4
Location: Edinburgh, Scotland
|
I was a bit concerned about running the 'Remove All Deployed Children' option because some of the documentation suggests that I have to redeploy the whole of the execution group, which i'm sort of trying to avoid.
Do you think this option would just remove the rogue message flows ? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Dec 14, 2005 4:54 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| alanjhunter wrote: |
I was a bit concerned about running the 'Remove All Deployed Children' option because some of the documentation suggests that I have to redeploy the whole of the execution group, which i'm sort of trying to avoid.
Do you think this option would just remove the rogue message flows ? |
Nope. You'll have to redeploy everything.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| alanjhunter |
| Posted: Wed Dec 14, 2005 6:35 am Post subject: |
|
|
Newbie
Joined: 07 Oct 2005
Posts: 4
Location: Edinburgh, Scotland
|
Thanks all for the replies.
Have started working on new '.bar' file in Toolkit to redeploy all the message flows to my broker. Will recreate the broker and then redeploy. Hopefully this will solve my problem. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Dec 14, 2005 7:52 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You shouldn't need to redeploy the entire broker. Just the bad EG.
Of course, if you only have one EG...
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
