MQSeries.net :: View topic - FileNode error handling and event monitoring

jsware

I am trying to use event monitoring to track files processed through message broker. When using the MQInput node, everything works as expected. With FileInput nodes, I seem to get a duplicate transaction start & rollback (even through I have set my FileInput node retry mechanism to failure).

My flow is basically:

MQInput -> Compute -> MQOutput
and a separate flow:
FileInput -> Compute -> FileOutput

Neither flows have catch or failure terminals wired up.
In both cases the compute just walks the tree to error on bad XML input.

On the MQ side, the backout queue attributes are configured, so the message processes, fails, and then on subsequent processing goes to the backout as expected.

On the file side, the retry mechanism on the Fileinput is set to failure. So the file gets read, fails and is moved to the mqsibackout folder. All good so far and working as expected.

Now I activate monitoring for the flow and subscribe a queue to the broker monitoring events. On the MQ side I get transaction start, rollback, start, end - what I would expect for get/fail, get/backout queue

As for File Input I get an additional start/rollback.. So I get start rollback, start,rollback, start end.

Why would I get a second start/rollback event when the FileInput node has the retry action to failure and the action on failing file set to move to mqsibackout?
_________________
Regards
John
The pain of low quaility far outlasts the joy of low price.