| Author |
Message
|
| Galichet |
 Posted: Tue Apr 05, 2005 5:55 am Post subject: How to delete an execution group with wbi V5 ? |
 |
|
Acolyte
Joined: 26 Jun 2001
Posts: 69
Location: Paris - France
|
Hi all,
I'm using WBI V5 CSD4 running on AIX 
A flow has been deployed with RAD in an execution group EG1
The same flow has been redeployed with a bar file in the execution group EG1.
Here is my problem :
I've noticed that the MQSeries input queue (used by this flow) had 2 input connection. After some verification, I've seen that the execution group EG1 was listed twice in the broker (with mqsilist) with a different ID... 
I imagine that was something special with the RAD deployed, but the problem right now is that I'm not able to delete this extra execution group ...  Even if I do a topology complete deploy, deletion of the execution group EG1, the extra EG1 execution group still remain on my broker. 
Do you have an idea how to delete it ? (I would prefer to avoid a broker delete/create...)
Thanks 
Eric
_________________
Eric Galichet
SMABTP
France |
|
| Back to top |
|
 |
| PGoodhart |
| Posted: Tue Apr 05, 2005 6:22 am Post subject: |
|
|
Master
Joined: 17 Jun 2004
Posts: 278
Location: Harrisburg PA
|
Search IBM MQSI support for "rogue execution group". There is a proceedure listed that will fix the problem.
_________________
Patrick Goodhart
MQ Admin/Web Developer/Consultant
WebSphere Application Server Admin |
|
| Back to top |
|
|
| Galichet |
| Posted: Tue Apr 05, 2005 6:46 am Post subject: |
|
|
Acolyte
Joined: 26 Jun 2001
Posts: 69
Location: Paris - France
|
Thanks a lot 
_________________
Eric Galichet
SMABTP
France |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Apr 05, 2005 8:14 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
And do a favor to the rest of us, and post the procedure here.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| JMB |
| Posted: Tue Apr 05, 2005 10:16 am Post subject: |
|
|
Apprentice
Joined: 01 Apr 2002
Posts: 29
|
|
| Back to top |
|
|
| mqmatt |
| Posted: Sat Apr 09, 2005 2:38 am Post subject: Re: How to delete an execution group with wbi V5 ? |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| Galichet wrote: |
Even if I do a topology complete deploy, deletion of the execution group EG1, the extra EG1 execution group still remain on my broker.
|
I see some confusion over when a complete or delta topology deploy is actually useful - thought this might clear things up:
Complete Topology Deploy
What does it do?
• Tells each broker in the domain the set of brokers with which it can share publish/subscribe information.
• If one or more brokers have recently been removed from the domain, this deploy type tells the brokers pending deletion to tidy up any resources. A successful completion of this tidy-up will cause the Configuration Manager to remove all references to the broker from its repository.
When to use it?
• If a broker’s publish/subscribe has become inconsistent (for example, if a broker is able to share publications with another, but not vice versa).
When NOT to use it?
• If you are adding brokers to the domain and you are not using publish/subscribe, a topology deploy is not required.
• If you are adding execution groups to a broker, a topology deploy is not required.
• If you have changed the publish/subscribe network, issue a delta topology deploy if possible, as this will only initiate a deployment to those brokers affected by the changes you have made.
• If you have removed a broker from the domain, a complete topology deploy will cause that broker’s resources to be tidied. However, it is preferable to use a delta topology deploy to do this instead, as these deploy types potentially affect fewer brokers in the domain.
Delta Topology Deploy
What does it do?
• Sends updated publish/subscribe network information to any broker whose publish/subscribe configuration (as determined by the Configuration Manager) is not up to date.
• If one or more brokers have recently been removed from the domain, this deploy type tells the brokers pending deletion to tidy up any resources. A successful completion of this tidy-up will cause the Configuration Manager to remove all references to the broker from its repository.
When to use it?
• If you have modified the publish/subscribe network.
• If you have deleted a broker from the domain and wish to tidy up its resources from within the Message Broker Toolkit.
When NOT to use it?
• If you are adding brokers to the domain and you are not using publish/subscribe, a topology deploy is not required.
• If you are adding or removing execution groups, a topology deploy is not important.
HTH
-Matt |
|
| Back to top |
|
|
| jfluitsm |
| Posted: Sun Apr 10, 2005 11:10 pm Post subject: |
|
|
Disciple
Joined: 24 Feb 2002
Posts: 160
Location: The Netherlands
|
What helps to prevent this kind of problems is to have an execution group for RAD only. If you want to use the same execution group, first remove all deployed children before deploying the bar file.
_________________
Jan Fluitsma
IBM Certified Solution Designer WebSphere MQ V6
IBM Certified Solution Developer WebSphere Message Broker V6 |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Apr 11, 2005 1:54 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
There has got to be a better way to get rid of a rogue EG. Bouncing the whole Broker is a bit disruptive, no?!?!
Also, is the reason for rogue EGs is a known defect that a soon to be released CSD will fix?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| PGoodhart |
| Posted: Tue Apr 12, 2005 3:40 am Post subject: |
|
|
Master
Joined: 17 Jun 2004
Posts: 278
Location: Harrisburg PA
|
I've found I can get into this state if I am deploying a large number of flows, and then the configuration manager and/or broker crashes in the middle of the process even though I am removing deployed children. (I am not sure there are every going to fix this 100%, as basically what happens is the broker database becomes inconsistant with the deployed objects. I have spent hours figuring out how to clean up this kind of mess, and honestly sometimes the IBM proceedure isn't enough.)
_________________
Patrick Goodhart
MQ Admin/Web Developer/Consultant
WebSphere Application Server Admin |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Apr 13, 2005 4:58 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| PGoodhart wrote: |
| I've found I can get into this state if I am deploying a large number of flows, and then the configuration manager and/or broker crashes in the middle of the process even though I am removing deployed children. (I am not sure there are every going to fix this 100%, as basically what happens is the broker database becomes inconsistant with the deployed objects. I have spent hours figuring out how to clean up this kind of mess, and honestly sometimes the IBM proceedure isn't enough.) |
I just don't understand why the ToolKit allows you to do things that can cause such a mess. For example, if you can only deploy x flows safely, then why doesn't the toolkit enforce that?
Lately it seems I have been getting a lot of calls...My ToolKit is hung...My debugger abended....my deploy timed out....I see my EGs more than once....
Common Solution? Bounce the Broker. Luckily these are SandBox Brokers and sometimes DEV (not QA or PROD), but still....
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| mqmatt |
| Posted: Thu Apr 14, 2005 2:38 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| PGoodhart wrote: |
| I've found I can get into this state if I am deploying a large number of flows, and then the configuration manager and/or broker crashes in the middle of the process even though I am removing deployed children. (I am not sure there are every going to fix this 100%, as basically what happens is the broker database becomes inconsistant with the deployed objects. I have spent hours figuring out how to clean up this kind of mess, and honestly sometimes the IBM proceedure isn't enough.) |
Do raise PMRs whenever you experience this; having components crash just isn't acceptable and it needs to get fixed.
Are there any specific crashes (error messages) you've encountered? |
|
| Back to top |
|
|
| PGoodhart |
| Posted: Thu Apr 14, 2005 3:58 am Post subject: |
|
|
Master
Joined: 17 Jun 2004
Posts: 278
Location: Harrisburg PA
|
All the crashes have been due to insufficent system resources, how is IBM going to PMR/APAR that?
_________________
Patrick Goodhart
MQ Admin/Web Developer/Consultant
WebSphere Application Server Admin |
|
| Back to top |
|
|
| mqmatt |
| Posted: Thu Apr 14, 2005 4:22 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| PGoodhart wrote: |
| All the crashes have been due to insufficent system resources, how is IBM going to PMR/APAR that? |
Agreed, although some abends are more graceful than others
Even with low system resources, your domain should never, ever get trashed. If it does, that's a data integrity defect - and a serious one at that. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Apr 14, 2005 11:32 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
|
| Back to top |
|
|
| mqmatt |
| Posted: Fri Apr 15, 2005 1:50 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
Hi Peter,
I don't have a definitive solution for you, but I've seen the problem you quoted if the Config Manager is on a different fixpack level to the tooling. First up, I'd suggest updating the CM or tooling to the same CSD.
-Matt |
|
| Back to top |
|
|
|
|
