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 » 2 process ids for 1 execution group

Post new topic  Reply to topic
 2 process ids for 1 execution group « View previous topic :: View next topic » 
Author Message
jbanoop
PostPosted: Mon Jul 10, 2006 1:37 am    Post subject: 2 process ids for 1 execution group Reply with quote

Chevalier

Joined: 17 Sep 2005
Posts: 401
Location: SC
Hi all,
We are facing a strange problem in production. We have an execution group called DonorInitiation. The mqsilist on the broker shows a process id of 26500.
However we were noticing that flows not visibly deployed to it (from toolkit) were getting executed on the execution group.

We did a grep on the DataFlowEngine processes and it turned up two processes with the same execution group name (DonorInitiation).
The process ids being 26500 and 45040.

It apparently seems that the 45040 process is the one which is actually running beneath the cover (the open handles on the input queues of the flows also confirms the suspicion).

How do you all suggest we go about rectifying the problem? Should we resort to killing 26500 or 45040 processes or both and hope for the auto restart of the execution group to fix it ?
It is a production system and we cannot afford to restart the broker .

The toolkit is 6.0.0.1 and broker version is 6.
Any help is highly appriciated.
Regards,
Anoop
Back to top
View user's profile Send private message Yahoo Messenger
AkankshA
PostPosted: Mon Jul 10, 2006 2:29 am    Post subject: Reply with quote

Grand Master

Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
I had faced the same problem in v5

Only killing the processes wont help as both ll come up on their own.


You need to restart the broker after killing them both
Back to top
View user's profile Send private message Visit poster's website
Bhawesh
PostPosted: Wed Jul 12, 2006 7:42 am    Post subject: Reply with quote

Newbie

Joined: 22 Oct 2002
Posts: 8
Location: NJ-NY-CT (USA)
I recently faced similar situation (though in QA) when two version of same flows were running in separate execution groups. The older flow was not visible from the toolkit, but after stoping the newer flow and restarting the broker, the messages were taken off the queue and gave same old result as what was expected of it. It was QA so coordinating to stop the broker was not that big a deal.

I had to kill the other execution group process. I also deleted that execution group from the toolkit and redeployed all the flows that were supposed to run on that execution group to another new execution group. I am not sure if all that ordeal was necessary but as I said it was QA and situation demanded a quick fix. I could have been more creative had it been in Production though.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » 2 process ids for 1 execution group
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.