MQSeries.net :: View topic - Catch terminal vs. transactional behavior

mmarq

I have a sub flow for error handling which reports in a system error file some trace information, creates and XML message to look at the errors and reports these errors on a FAILURE queue prior to a throw node to roll the exception back.

I'm hoping if say a database error happens along the way or a network timeout, this sub-flow will be triggered, it will throw control back to the INPUT node for 3 retries and then write out to my configured backout requeue name value. The message flow is transactional and single threaded (only one instance).

If I attach this message flow to the Input node catch terminal it looks like (according to the Problem Determination Guide) that if an error occurs like a db error it will rollback to the catch terminal and then (the way I have this configured) record the error cause a THROW and subsequence rollback but now what happens? Does it go back to the catch terminal again or because it is transactional will it do the retry and then when retries are exceed end up on my backout requeue?

In general, I'm looking for a rollback to the input node (all db txns do not commit), report what happened, retry 3 times and then hit the retry queue.

Can I achieve this? Also, to achieve this behavior it appears from the documentation that I would not attach any other error handling to say the fail terminals in my primary and sub flows. e.g., that the single error handler at the catch terminal on the input node is sufficient.

Thanks in advance,
Melissa

NerveWire, Inc.
www.nervewire.com
_________________
M Marquis