When you design your message flow, consider which terminals on the input node to connect:
All input nodes process non-transactional, non-persistent messages. The built-in input nodes handle failures and exceptions associated with these messages in this way:
The Real-timeInput and Real-timeOptimizedFlow nodes retry once before they discard the message; that is, they retrieve the message again and attempt to process it.
The SCADAInput node does not propagate the message to the failure terminal if an exception is generated in the catch flow. The node logs the error in the local error log and discards the message.
This action is summarized in the table below:
Error event | Failure terminal connected | Failure terminal not connected | Catch terminal connected | Catch terminal not connected |
---|---|---|---|---|
Node detects internal error | Fail flow handles the error | Node logs the error and discards the message | Not applicable | Not applicable |
Node propagates message to out terminal, exception occurs in out flow | Not applicable | Not applicable | Catch flow handles the error | Node logs the error and discards the message |
Node propagates message to catch terminal, exception occurs in catch flow | Fail flow handles the error (not SCADAInput) | Node logs the error and discards the message | Not applicable | Not applicable |
Node propagates message to failure terminal, exception occurs in fail flow | Not applicable | Not applicable | Node logs the error and discards the message | Node logs the error and discards the message |
Related concepts
Message flows
Message flow application deployment
Related tasks
Using subflows
Creating a message flow
Defining message flow content
Editing configurable properties
Related reference
Built-in nodes
WebSphere MQ Enterprise Transport
WebSphere MQ Mobile Transport
WebSphere MQ Multicast Transport
WebSphere MQ Real-time Transport
WebSphere MQ Telemetry Transport
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac18890_ |