| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Execution Group Abend when running Aggregate flow |
« View previous topic :: View next topic » |
| Author |
Message
|
| jbanoop |
 Posted: Mon May 29, 2006 7:53 am Post subject: Execution Group Abend when running Aggregate flow |
 |
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
Hi,
We are faced with a weird problem here. We have a flow which does some validations on the incoming message. These validations are done using agrregation with the aggregation reply queue also in the same flow.
The issue we are having is that when we attach the debugger and test the flow everything goes picture perfect.
However if we detach the debugger and test the same the execution group abends with a dmp file being created.
Our config here is toolkit 6.0 with the broker running on XP.
By the way the only thing i could make out form the abend file created was "access Violation- could not read <some mem loc name>".
We have tried, restarting the broker, machine to no avail. Any inputs to this would be really helpful. Do let me know if I need to provide any more details.
Regards,
Anoop |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue May 30, 2006 4:55 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You should apply the latest broker runtime fixpack.
And the latest broker toolkit fixpack.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jbanoop |
| Posted: Wed May 31, 2006 5:47 am Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
Hi,
Just fixed the issue. The problem was that after receiving the aggregate reply, the aggregated reply was being propagated till the point where a new message was being created (and this ewas just before putting it on the output queue).
When the code was changed so that the output of the aggregate reply node was used to create a valid MQ message (with MQMD and Properties) in a compute node just after the aggregate reply node, the problem stopped.
However I cannot still finda reason why this scenario worked when debugger was attached and not when the debugger was removed.
Regards,
Anoop |
|
| 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
|
|
|
|
