| Author |
Message
|
| scaryjase |
 Posted: Thu Jul 17, 2003 5:05 am Post subject: deleting execution groups |
 |
|
Novice
Joined: 17 Jul 2003
Posts: 22
|
am i correct in thinking that in order to fully get rid of an execution group from a broker, you have to check out the broker, delete the execution group and then do a full deploy on the broker?
i ask because we are currently unable to do a full deploy due to us reaching a restriction on the heap size (it transpires we have slightly more on our brokers than most people, shall we say), so we have a load of unwanted execution groups still deployed on our broker that we are unable to shift.
_________________
scary |
|
| Back to top |
|
 |
| EddieA |
| Posted: Thu Jul 17, 2003 7:37 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
You should be able to do a Delta deploy at the Broker level.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| scaryjase |
| Posted: Thu Jul 17, 2003 8:00 am Post subject: |
|
|
Novice
Joined: 17 Jul 2003
Posts: 22
|
i agree i should be able to. but i can't...
i get the not enough storage available on "APP_CTL_HEAP" message, and our heap size is set to BIG!!
_________________
scary |
|
| Back to top |
|
|
| kirani |
| Posted: Thu Jul 17, 2003 10:28 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Did you try increasing your Config Managers JVM Heap size to higher value? Doing delta deploy of each EG might help.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| scaryjase |
| Posted: Thu Jul 17, 2003 10:41 am Post subject: |
|
|
Novice
Joined: 17 Jul 2003
Posts: 22
|
i'm told my heap size is as big as anyone could ever want it to be!! have actually solved it now - removed nearly all message sets and flows from the broker and managed to do a delta deploy on the broker and all the rubbish disappeared. then added everything back in again.
not big and not clever, i realise...
_________________
scary |
|
| Back to top |
|
|
| rajmq |
| Posted: Thu Jul 17, 2003 9:52 pm Post subject: |
|
|
Partisan
Joined: 29 Sep 2002
Posts: 331
Location: USA
|
Hi
How to increase Config Manager JVM Heap size??
regards
raj |
|
| Back to top |
|
|
| kirani |
| Posted: Thu Jul 17, 2003 10:37 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
use mqsichangeconfigmgr command with -j option.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| michaelpatton |
| Posted: Tue Jul 29, 2003 3:09 pm Post subject: Deleteing and Unresponsive EG |
|
|
Apprentice
Joined: 21 May 2002
Posts: 25
Location: East Coast USA
|
| How about deleteing an EG from a broker, where the EG in question is unresponsive? All the other EGs in the broker respond fine, except the one I want to delete. (I think it is caught up in a bad java plugin) Simply deploying the deleteion message, and the EG response times out. I do not want to have to delete the entire broker and rebuild if I can avoid it. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Jul 30, 2003 11:03 am Post subject: Re: Deleteing and Unresponsive EG |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| michaelpatton wrote: |
| How about deleteing an EG from a broker, where the EG in question is unresponsive? All the other EGs in the broker respond fine, except the one I want to delete. (I think it is caught up in a bad java plugin) Simply deploying the deleteion message, and the EG response times out. I do not want to have to delete the entire broker and rebuild if I can avoid it. |
If the EG is stuck in a loop, and unresponsive, it won't respond to the request to delete it.
You'll need to break it out of the loop. You might be able to get it to break out by telling it to stop all message flows.
If that doesn't work, you'll have to kill it's process. You can find out which PID belongs to which EG by using "mqsilist <broker-name>". Killing the execution group process will not cause it to permanantly halt, merely stop and get restarted by the broker. If your EG is stuck in a loop trying to process a message, and the message is still on the input queue when you restart the EG, the EG will get stuck again. So make sure you clear any pending messages. |
|
| Back to top |
|
|
| kirani |
| Posted: Wed Jul 30, 2003 12:50 pm Post subject: Re: Deleteing and Unresponsive EG |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
| michaelpatton wrote: |
| How about deleteing an EG from a broker, where the EG in question is unresponsive? All the other EGs in the broker respond fine, except the one I want to delete. (I think it is caught up in a bad java plugin) Simply deploying the deleteion message, and the EG response times out. I do not want to have to delete the entire broker and rebuild if I can avoid it. |
The safest way is to disable the input queue first and then kill the EG process. After this the current message that's being processed by the Message flow will be rolled back to the input queue. So next time when the EG starts it will not pickup any message for processing. Now stop all your message flow and then delete the EG.
If you think it's a plug-in problem then I'd not recommed that you delete the EG, instead you can remove the plug-in jar file from the lil directory before restarting the broker. Once the broker is restarted, remove the message flow which uses this plug-in node from the EG and then deploy the changes once again.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
|
|
