| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Execution Group Hide and Seek |
« View previous topic :: View next topic » |
| Author |
Message
|
| JohanSwanepoel |
 Posted: Mon Jul 13, 2009 9:43 pm Post subject: Execution Group Hide and Seek |
 |
|
Newbie
Joined: 12 May 2009
Posts: 4
|
G'day
I have been a reading member of this forum for a long time, and have come across an ineteresting issue on one of my Message Brokers.
Description:
Running mqsilist [Broker name] -e [EG Name] shows me all the contents of an execution group.
Trying to deploy/undeploy to this execution group gives "BIP1038S: Execution group not found... was not found in the Configuration Manager repository for broker ... or you do not have the required permissions to view it"
I find this strange as I previously had permissions. The user that I am using has full permissions on the Configuration Manager Proxy and all the objects in it.
The IBM Documentation is not very useful as it only states that the user, ie me, needs to pick a execution group that exists  Not very helpful in this case 
The closest information that I found was on here about Phantom Execution groups, but I am not sure if it applies to this problem.
The broker version is 6.1.0.2, and I have looked into the logs and it is not showing any information about the deployment process.
Any help will be much appreciated
Regards |
|
| Back to top |
|
 |
| vmcgloin |
| Posted: Mon Jul 13, 2009 11:25 pm Post subject: |
|
|
Knight
Joined: 04 Apr 2002
Posts: 560
Location: Scotland
|
Hi,
Have you verified the permissions that user ID has at the broker level using mqsilistaclentry? I assume you have, but it is not clear from what you say. |
|
| Back to top |
|
|
| JohanSwanepoel |
| Posted: Tue Jul 14, 2009 2:34 pm Post subject: |
|
|
Newbie
Joined: 12 May 2009
Posts: 4
|
Hi,
Yes permissions is fine; it is something that was working before and stopped for no apparent reason at all.
I am hoping that I do not have to recreate the broker |
|
| Back to top |
|
|
| nvenkatesh |
| Posted: Tue Jul 14, 2009 11:36 pm Post subject: |
|
|
Apprentice
Joined: 29 Jan 2007
Posts: 45
|
Hi,
What might have happened in your case is that the details of the EG has been deleted from the configuration repository but not yet deleted from the broker database. There are 2 possible reasons for this to happen.
1) The channel between your config manager and broker is broken.
The solution is to fix the channel and verify whether it is running properly. When you do so the EG will be automatically deleted from the broker db.
2) You tried to delete the EG while the flow is still running (i.e The flow has gone in to infinite loop or flow is holding the handles of external resources which it cant cleanup for some reasons or simply the flow is irresponsive) which means the EG holding the flow cant process the "delete EG configuration message" at that time. In this case you would see that the EG has been deleted from your toolkit(Configmgr) but not actually deleted from the broker db. Certain commands fulfill their requests via config manager(mqsideploy) and some commands directly send their request to the broker(mqsilist -e). Thats why you see the inconsistency.
The solution to this situation is that you have to remove all the messages from the input queue of your flow(so that invocation of your flow is avoided), kill DFE process so that it automatically restarts. Now you might see your EG will get deleted from the broker which depends on the availability of "delete EG configuration message"(which you sent while deleting the EG) to the broker DFE when it restarts, if this did not happen you have to restart both the config manager and the broker, Now you will see that your EG has been recovered in the config manager(also in the toolkit) as it will discover components automatically when it finds inconsistency while restarting.
Thanks,
Venkatesh |
|
| Back to top |
|
|
| JohanSwanepoel |
| Posted: Sun Jul 19, 2009 9:54 pm Post subject: |
|
|
Newbie
Joined: 12 May 2009
Posts: 4
|
Hi
Thanks for all the advise,
The solution ended up being fairly simple. I connected to the Configuration Manager through the WMB toolkit and the Execution Groups was shown as DiscoveredEG_[Some number], so I renamed them to have the proper names again and can now perform the requried administration. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
