| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| exec stop error |
« View previous topic :: View next topic » |
| Author |
Message
|
| madi |
 Posted: Mon Jun 12, 2006 9:26 am Post subject: exec stop error |
 |
|
Chevalier
Joined: 17 Jan 2006
Posts: 475
|
Hi All
I had some problems installing v 6.0 and after many effort it finally worked when I created the config mgr and the broker on two different QMs.
The problem started when on of my flows had some exception in it.
I was using the debugger to see what it was and even though I clicked 'Run To Completion' the exception coming back again and again and again ... so I disconnected the debugger and everything just bombed 
now, i cannot connect to the broker, cannot stop it and ofcourse cannot deploy any flows to it
i can see this error in the event log
| Quote: |
( RB_BROKER_1 ) The broker has detected that Execution Group 'default', process ID '2572', has not shutdown.
An attempt was made to stop an Execution Group process by issuing an internal configuration message to the Execution Group. The Execution Group process has not yet shut down.
Use the system Log to investigate why the Execution Group process could not shutdown. It is expected that the Execution Group will eventually shutdown normally. This message is repeated at 1 minute intervals. However, it is possible that you may need to stop the Execution Group manually. If the broker was configured as a WebSphere MQ trusted application then refer to the WebSphere MQ reference manuals to determine how to stop the Execution Group executable. Ensure that any database locks held by the Execution Group are released if the process is forced. Contact your IBM support center if you are unable to determine the reason for this problem. |
can somebody tell what could be wrong??
--madi |
|
| Back to top |
|
 |
| JT |
| Posted: Tue Jun 13, 2006 8:14 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
Check the CPU usage of the DataFlowEngine, you're probably in a loop.
Kill the pid of the DFE, then issue an mqsireload of the execution group or restart the broker. Also, ensure the message wasn't rolled-back to the input queue, if so remove it. |
|
| Back to top |
|
|
| mqmatt |
| Posted: Tue Jun 13, 2006 9:43 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
|
| Back to top |
|
|
| madi |
| Posted: Tue Jun 13, 2006 11:52 am Post subject: |
|
|
Chevalier
Joined: 17 Jan 2006
Posts: 475
|
Done all that but still have this error
i created another broker for now and working in that
i tried to delete the broker but the command just hangs up and nothing happens!!
--madi |
|
| 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
|
|
|
|
