MQSeries.net :: View topic - Multiple SOAP Fault messages generated

rdg · Posted: Fri Dec 03, 2010 2:12 am Post subject: Fixed via APAR IC70662

I have the following Message Flow layout...

SOAP Input Node -> General Transformation Node(s) -> SOAP Reply Node

The SOAP Input Node has its 'Catch' terminal connected and the message flow takes some general action to log the exceptions that it catches here (outside of transaction control i.e. non-transactionally).

After logging the exception, I want to (re)throw an exception, using a throw node in order to force a rollback and subsequently stop processing within the flow.

Problem:

When using a SOAP Input node when you (re)throw the exception, the SOAP Input node automatically generates a (second) SOAP fault response using the exceptions list to send back to the consumer of the service.

This behaviour of sending back a response to the service consumer does not occur when using an MQ Input node, where (re)throwing an exception to force a rollback within a catch is common practice.

I do not want the SOAP Input node to send back a SOAP fault response to my service consumer, because I have taken care to send a custom SOAP fault response myself during my 'catch' processing. The fact that the SOAP Input attempts to generate a SOAP fault response for me is causing a secondary error because I have already used up the SOAP reply identifier when I sent my custom SOAP fault response.

Is there any method / fix pack etc that would allow me to stop the SOAP Input node from attempting to send back a SOAP fault response for me?