ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » START EXECUTIONGROUP loop

Post new topic  Reply to topic
 START EXECUTIONGROUP loop « View previous topic :: View next topic » 
Author Message
francoisvdm
PostPosted: Tue Jul 21, 2009 1:45 am    Post subject: START EXECUTIONGROUP loop Reply with quote

Partisan

Joined: 09 Aug 2001
Posts: 332

BROKER V6.1 fixpack 3 on Windows

I see the following "command" every few minutes in the SYSTEM.BROKER.EXECUTIONGROUP.QUEUE

Code:
<Broker uuid="638b5942-2001-0000-0080-dc04cd90b1d2" label="BROKER3"><Start><ExecutionGroup uuid="d3103d61-2001-0000-0080-931c02b13e21" label="DEV"/></Start></Broker>


All message flows in "DEV" executiongroup is running. The DEV uuid in the command above is the one assigned to the EG in the BROKERAAEG DB. But, then every few minutes I get error message in windows event viewer stating that in internal START message for DEV failed. Any ideas? How can I stop this message from appearing every few minutes?

To me it looks like the broker thinks this EG is not running, so it is trying to start it periodically.
_________________
If you do not know the answer or you get the urge to answer with "RTFM" or "Search better in this forum", please refrain from doing so, just move on to the next question. Much appreciated.

Francois van der Merwe
Back to top
View user's profile Send private message Send e-mail
francoisvdm
PostPosted: Tue Jul 21, 2009 2:04 am    Post subject: Reply with quote

Partisan

Joined: 09 Aug 2001
Posts: 332

hmm, looks like that executiongroup is truly broken... it shows "running" in the toolkit..but that is all.

When I do mqsilist BROKER -e DEV it timeout after 360 seconds while this command is working 100% for other EGs.

I tried to stop flows in EG...not working.
I tried to delete EG...not working.

Guess I'm back to fiddling with DB to try and get rid of this EG...sigh
_________________
If you do not know the answer or you get the urge to answer with "RTFM" or "Search better in this forum", please refrain from doing so, just move on to the next question. Much appreciated.

Francois van der Merwe
Back to top
View user's profile Send private message Send e-mail
Vitor
PostPosted: Tue Jul 21, 2009 2:47 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

francoisvdm wrote:
Guess I'm back to fiddling with DB to try and get rid of this EG...sigh


You might want to practice by defusing live bombs before you try that!

"Fiddling" is always risky. Make sure you've exhausted all the other options for removing phantom execution groups discussed in here before you get creative.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
nvenkatesh
PostPosted: Tue Jul 21, 2009 3:02 am    Post subject: Reply with quote

Apprentice

Joined: 29 Jan 2007
Posts: 45

Hi,

It looks like your flow in that particular EG has gone into an infininite loop or the flow holds some external resources which it could not get rid of(For e.g the flow is in the debug session).

I think you have to remove all the inputs to the flows in the EG, stop debug session and kill the DataFlowEngine of that particular EG. Due to the resilient nature of the DFE, it automatically restarts. After that you can perform all the operations since the flow has stopped running.

Thanks,
Venkatesh
Back to top
View user's profile Send private message
francoisvdm
PostPosted: Wed Jul 22, 2009 10:32 pm    Post subject: Reply with quote

Partisan

Joined: 09 Aug 2001
Posts: 332

I could not confirm that flow was in loop...so in the end I decided to cut the blue wire....

1. I used MQSILIST BROKER to find the process IDs
2. Then, I removed that line from the BROKERAAEG DB while broker was running
3. I stopped broker and killed last message flow engine that did not want to stop from task manager.
4. I removed ALL MQ messages from ALL SYSTEM.BROKER.* queues
5. Restarted everything
6. Did full topology deploy from domain view.

Maybe I was lucky...but it worked.
_________________
If you do not know the answer or you get the urge to answer with "RTFM" or "Search better in this forum", please refrain from doing so, just move on to the next question. Much appreciated.

Francois van der Merwe
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » START EXECUTIONGROUP loop
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.