MQSeries.net :: View topic

srinii2005 · Posted: Fri Jul 25, 2014 5:56 am Post subject:

I have a message flow which has MQ input Node MQInput node is connected to Out, Failure and Catch terminal. I have handled the exceptions for Input Schema validation in the failure terminal. I have used XSD for validation of input XML. I gave incorrect element and the flow is sending messages to back out queue instead of sending the error message as"input schema validation failed" which i have handled in failure terminal.
This is going to back out queue only in region where the MQ is clustered. In Dev region and Local the error message is correctly displayed. I would like to know why the message is going to back out queue despite handling the error in code.
I have set the MQ Input node properties Parser Options as "Immediate" and Advanced Transaction Mode as "Yes".
I have enabled the user trace and here is the snipped of error from that.
Node '' has received a message, but an exception was generated whilst initializing it's internal representation. The failure terminal is attached but previous attempts to successfully process this message down this terminal have failed. The MQMD ''backoutCount'' of the message now equals the ''backoutThreshold'' defined for the WebSphere MQ input queue. Having now reached the ''attempt limit'' for processing the message down the failure terminal, the message broker is now putting the message to the requeue or dead letter backout queue associated with this node.
If 'complete' or 'immediate' MRM, DFDL, JSON or XMLNSC message body validation is being applied to messages received by this node, it's possible the format of the body of the received message is invalid. Examine further messages to confirm this. Also, examine previous messages to determine why the exception is not being successfully processed when routed down the failure terminal. Correct these situations if possible. Perform any local error recovery processing required.