| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Aggregate Reply, Timeout Exception |
« View previous topic :: View next topic » |
| Author |
Message
|
| raghubegur |
 Posted: Fri Apr 14, 2006 1:34 pm Post subject: Aggregate Reply, Timeout Exception |
 |
|
Apprentice
Joined: 15 Jul 2002
Posts: 45
|
Hi,
WBIMB : 6.0.0.0
AggregateReplyNode : Timeout terminal connected to a compute node where I throw a exception.
AggregateReplyNode : Catch terminal connected to myexceptionHandler.
Whenever there is a aggregate timeout, the msg reaches the compute node where I throw the exception. The msg then is expected to take the catch path. But it is going back to the timeout path. Infinite loop.
Any answers ?
Cheers,
Raghu
_________________
Cheers
Raghu |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Apr 14, 2006 1:39 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
|
| Back to top |
|
|
| raghubegur |
| Posted: Fri Apr 14, 2006 3:58 pm Post subject: |
|
|
Apprentice
Joined: 15 Jul 2002
Posts: 45
|
Hi,
I understand that. The catch terminal is connected to my error handling routine which currently handles all exceptions thrown anywhere in my flow.
The problem is this : When I throw an exception down the 'TimeOut' path the message is getting rolled back to the aggregate reply node. The behaviour then, per documentation, should be to take the 'catch' path. It is NOT happening. It is going again on the 'TimeOut' thus creating a infinite loop.
Cheers,
Raghu |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Apr 14, 2006 5:33 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| raghubegur wrote: |
| When I throw an exception down the 'TimeOut' |
| jefflowrey wrote: |
| If a message sent down the timeout thread causes an exception |
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| raghubegur |
| Posted: Fri Apr 14, 2006 7:09 pm Post subject: |
|
|
Apprentice
Joined: 15 Jul 2002
Posts: 45
|
| Code: |
| If this(CATCH) terminal is either unattached or an exception occurs while processing the message, the timeout is rolled back onto the internal queue and is reprocessed |
The catch terminal is attached to a error handler. There is no exception condition within the error handler.
Thanks,
Raghu |
|
| 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
|
|
|
|
