MQSeries.net :: View topic - JMSProvider and JMSOutput Node Error Handling

cc

I have a simple message flow that has an MQInput Node -> Compute Node -> MQJMSTranform Node -> JMSOutput Node. I have been running some unit tests to determine what I need in my Error handling logic and I am surprised by the behavior of this flow and wanted to get some other peoples thoughts.

When I introduce an error in the JMS Connection, i.e. invalid hostname or port for Provider URL, an Exception is thrown when the message flow GET's the message from the input queue and not when the JMSOutput Node tries to PUT the message to the JMS Provider. Therefore, the WMB Error handling is treated as if an MQInput Node Internal Error occured, the message is Propagated straight to the Failure Terminal, and not as if the error occured downstream from the Out Terminal. This seems counter intuitive to what I was expecting. My major concern is that this behavior may change in the future and therefore my current strategy for Error Handling may break.

Anyone have any ideas why this is occuring? Whether this is consistent with what they would expect?

I am running WMB V6.1.0.5 on AIX and the JMS Provider is ActiveMQ.