|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Remove orphan execution group process |
« View previous topic :: View next topic » |
Author |
Message
|
Bosco |
Posted: Thu Mar 11, 2004 9:57 pm Post subject: Remove orphan execution group process |
|
|
Novice
Joined: 30 Nov 2003 Posts: 17
|
Hi,
During a message flow deployment to an execution, there was an out of memory problem on my PC. The configuration returned an error message to that effect. In the Broker Admin -> Domains perspective, there was nothing in the execution group and an indicator showed it was stopped. However, when I did a MQSILIST broker, the execution group was actually running, and there was a process id associated.
I can't find a way to remove the execution group. Every time I ended the process in Windows Task Manager, it automatically comes back.
How can I remove it?
Bosco |
|
Back to top |
|
 |
kirani |
Posted: Thu Mar 11, 2004 11:19 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001 Posts: 3779 Location: Torrance, CA, USA
|
You didn't provide your platform details (CSD level etc). When bipservice process detects an execution group process has ended, it will try to create a new instance of that EG, so you will always see an EG process in Task Manager while the broker is running. _________________ 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 |
|
 |
Bosco |
Posted: Sun Mar 14, 2004 1:55 pm Post subject: |
|
|
Novice
Joined: 30 Nov 2003 Posts: 17
|
Hi Kirani,
my platform is WBIMB version 5.0.2 with CSD2 installed.
Thanks
Bosco |
|
Back to top |
|
 |
JLRowe |
Posted: Tue Mar 16, 2004 4:05 am Post subject: |
|
|
 Yatiri
Joined: 25 May 2002 Posts: 664 Location: South East London
|
I also have had problems with orphaned execution groups in WBIMB 5.0.2, and not after an error.
I have tried to report a bug, but cannot consistently replicate the problem. |
|
Back to top |
|
 |
waugh |
Posted: Fri Mar 26, 2004 1:34 pm Post subject: |
|
|
 Master
Joined: 19 Feb 2004 Posts: 225
|
went into the configmgr database and deleted records for that exceution group for that UUID in some of the tables and the problem was fixed for now. But, when i spoke to IBM, they are not advising this solution.  |
|
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
|
|
|
|