| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WBIMB 5.0 message flow is not running |
« View previous topic :: View next topic » |
| Author |
Message
|
| venkat kurra |
 Posted: Mon May 02, 2005 7:16 am Post subject: WBIMB 5.0 message flow is not running |
 |
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
Hi,
One of the message flows stopped automatically in our WBIMB/CSD4 environment. The Event Viewer application log displays the time out error for that execution group.
( HIGMQIXA ) Execution Group TEST_EXGRP failed to return an internal configuration Start message response within a 60 second time period.
The internal configuration message response could not be retrieved. The Execution Group therefore failed to move to the state described by the internal configuration message.
Investigate why the Execution Group internal configuration message response was not returned within the allowed time period by reviewing messages issued to the system log. Additionally, you can increase (or decrease) the timeout by using the mqsichangebroker option, ConfigurationDelayTimeout. This will not resolve any underlying problem with a deployed configuration message, but can be used to reduce the response turnaround time or allow for large and complex deployments. Resolve any problems described in the system log. This 'internal configuration' operation will be retried automatically, if you continue to see this message you should investigate the reason for the Execution Groups failure to respond.
The flow is not starting even we start manually.
We went through the whole application log and found that all execution groups on that broker had time out in the early morning. Actually no one did a deploy or make a change at that time. Finally i killed the execution group process from the Task manager(Windows) and then the flow started automatically.
Why the flow stops itself? Any Experience!
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
 |
| _dave_ |
| Posted: Tue May 03, 2005 12:27 am Post subject: |
|
|
Apprentice
Joined: 08 Apr 2005
Posts: 33
Location: IBM Hursley
|
The message you mention is written by the bipbroker process. This is the process that spawns the DataFlowEngine (execution group) processes. It expects to receive a response within the allocated time period from the execution group process it has started.
A few things to check:
- Were there any messages in the event log reporting any errors prior to the one you mention ? (specifically from the execution group process) If so what were they?
- Did the execution group process actually start OK but did it just take a long time? To know you can check the use count of the input queue. If someone has the input queue open then it is likely that the execution group started OK.
- Were there others execution groups starting at the same time which were stressing the system? This could result in an overall increase in the amount of time the processes take to start. |
|
| Back to top |
|
|
| venkat kurra |
| Posted: Tue May 03, 2005 8:02 am Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
Dave, Thanks for your responce. We double check the Event viewer and found some access vilation errors and it might be caused the process shutdown.
An internal WebSphere MQ error has occurred (Access Violation at address 0D158000 when reading)
MQ detected an unexpected error when calling the operating system. The MQ error recording routine has been called.
Use the standard facilities supplied with your system to record the problem identifier, and to save the generated output files. Contact your IBM support center. Do not discard these files until the problem has been resolved.
An error has been detected, and the WebSphere MQ error recording routine has been called. The failing process is process 7216.
(process 7216 was the TEST_EXGRP)
Then it assigned a different process id for this execution group but i was not able to start the flow. Finally i killed the process id to make it work.
Right now we are ok but we didn't know why the flow was stopped.
We got an FDC and it show some thing about APIExit,which is configured on this queue manager . We are still working with the API Exit Vendor.
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
| _dave_ |
| Posted: Tue May 03, 2005 8:15 am Post subject: |
|
|
Apprentice
Joined: 08 Apr 2005
Posts: 33
Location: IBM Hursley
|
It's likely that the MQ error you describe will cause the execution group process to terminate.
The bipbroker process that starts and monitors execution group processes will attempt to restart the process if it considers that it has terminated unexpectedly. This would explain why the process number was different. The bipbroker process normally outputs a message to say that an execution group terminated unexpectedly and is restarting it.
The MQ error you mention sounds pretty severe and you are right to get this sorted out first. If you get any more probs once this is fixed then you know where to post  |
|
| Back to top |
|
|
| venkat kurra |
| Posted: Wed May 11, 2005 5:39 am Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
Dave,
We got a latest APIExit to capture more information if the problem repeat again. As of now we did not find any reason even with those FDC files. We are just waiting(hopefully it won't happen again).
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| 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
|
|
|
|
