| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| execution group auto restarts |
« View previous topic :: View next topic » |
| Author |
Message
|
| RaviKrG |
 Posted: Sat Mar 07, 2009 3:23 pm Post subject: execution group auto restarts |
 |
|
Master
Joined: 07 Sep 2008
Posts: 240
|
Hi,
Everytime a message is backed out and when we check the broker log we find that the time message is backed out the execution group was restarted automatically. I find the logs as
Severe error: /build/S500_P/src/CommonServices/Unix/ImbAbend.cpp 515 signal received Abend file: /var/mqsi/errors/BRKR.7f8a6ffc-1901-0000-0080-d51319f22e3a.13826.23.abend action: abort
Error encountered during abend processing: Function ImbAbend::signalHandlerInternal() - terminating
The broker has detected that the Execution Group processgroup, process ID 826, has shutdown. : BRKR.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 3894: ImbAdminAgent::startAndMonitorADataFlowEngine: :
Execution Group started: process '6296'; thread '1'; additional information: brokerName 'BRKR'; executionGroupUUID '7f8a6ffc-1901-0000-0080-d51319f22e3a'; executionGroupLabel 'processgroup'; defaultExecutionGroup 'false'; queueManagerName 'BRKRQM'; trusted 'false'; dataSourceName 'BRKRDB'; userId 'wmbuser'; migrationNeeded 'false'; brokerUUID '413ecbfb-1901-0000-0080-d51319f22e3a'; filePath '/opt/mqsi'; workPath '/var/mqsi'. : BRKR.7f8a6ffc-1901-0000-0080-d51319f22e3a: /build/S500_P/src/DataFlowEngine/ImbMain.cpp: 243: main: :
Can any body tell why this is happening with this execution group and not with others as I have aroung 6 more execution groups running but this is the only execution group which shuts down and restarts automatically.
Thanks |
|
| Back to top |
|
 |
| rekarm01 |
| Posted: Sun Mar 08, 2009 1:17 pm Post subject: Re: execution group auto restarts |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
The execution group process shut down because it received a fatal signal from the OS, for any one of a number of reasons, such as a stack overflow, out-of-memory error, floating point exception, etc. When the broker detects that an execution group shut down, it will automatically restart it.
The abend file (/var/mqsi/errors/BRKR.7f8a6ffc-1901-0000-0080-d51319f22e3a.13826.23.abend) provides additional information, such as which signal was received. It also contains a lot of other information that this forum can't help you with, so please don't post the entire file.
A likely cause of the fatal signal is a bug in one or more message flows deployed to that execution group. |
|
| Back to top |
|
|
| RaviKrG |
| Posted: Sun Mar 08, 2009 2:39 pm Post subject: |
|
|
Master
Joined: 07 Sep 2008
Posts: 240
|
Thanks rekarm01, but I have few questions
1)any idea to how can we read that file
2) the generated is of zero size during this error throw |
|
| Back to top |
|
|
| RaviKrG |
| Posted: Sun Mar 08, 2009 3:16 pm Post subject: |
|
|
Master
Joined: 07 Sep 2008
Posts: 240
|
|
| Back to top |
|
|
| Hari |
| Posted: Sun Mar 08, 2009 3:19 pm Post subject: |
|
|
Centurion
Joined: 21 Nov 2002
Posts: 117
Location: USA
|
The abend file, as already stated contains lot of additional info which is IBM specific, if you plan to look at it yourself and resolve your issue it wont help much.
Also check your syslog.
I will second rekarm01 statement, that there is a bug in your msg flow/s that have been deployed to this EG. Start by identifying the msg flow/node causing the abend and try it to resolve it from there. |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Sun Mar 08, 2009 6:05 pm Post subject: Re: Post subject: execution group auto restarts |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| RaviKrG wrote: |
| 2) the generated is of zero size during this error throw |
Was that a question?
Which signal does the abend file report that the execution group received? That might be useful. Depending on the signal, other information in the abend file (such as a thread's stack trace) might or might not also be useful.
If the OS is sending fatal signals to kill a process, that means that the message flow(s) or broker are failing to detect any relevant errors beforehand, and handling them in a more graceful manner, such as by throwing an exception. This may make it more difficult to find the root cause of the errors. |
|
| 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
|
|
|
|
