MQSeries.net :: View topic - SOAP Fault handling

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » SOAP Fault handling

SOAP Fault handling

« View previous topic :: View next topic »

Author

Message

marko.pitkanen

Posted: Thu Jun 04, 2009 10:29 am Post subject: SOAP Fault handling

Chevalier

Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland

Hi,

I wonder what is the preferred way to handle SOAP Faults in the following scenario:

MQInput -> compute -> SOAPRequest -> compute -> MQOutput

What I have tried is

Code:

> MQOutput
/
MQInput -> compute -> SOAPRequest -> compute -> MQOutput
\ \
\ > compute_store_soap_fault -> throw
\
> compute_create_message_to_error_monitoring -> MQOutput -> Throw

Basically I store the SOAP Fault message to the Environment in compute_store_soap_fault node. Then rollback the execution to the MQInput's catch terminal and process error message for the error monitoring and rollback the original message starting the execution of the flow to the queue for the further investigation and reprocessing.

No I'm facing the situation that after SOAP fault it seems that flow goes to the unstable state and for next messages I'm encountering unexpected errors like "An invalid XML character (Unicode: 0xef) was found in the prolog of the document ... /Root/XMLNSC" or "ParserException BIP5025E: XML schema validation error ''Unexpected root tag. Element "XXXX" is not a global element.'' on line '1' column '56' when parsing element ''/Root/XMLNSC''. Internal error codes: 5032, 2.
This error was reported by the XMLNSC parser. The XML document being parsed is not valid according to the message definitions in the message set.
The XML document has violated the rules expressed in the message definition files in the message set." when accessing elements from SOAP Response or the original message.

Running the mqsireload command fix the situation.

My broker version is 6103 and OS's are AIX or windows.

Marko

WMBDEV1

Posted: Thu Jun 04, 2009 11:58 pm Post subject:

Sentinel

Joined: 05 Mar 2009
Posts: 888
Location: UK

It may be time for a PMR?

Looking at the stuff you are doing I wouldnt expect it to corrupt all the future requests until the EG is reloaded.

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » SOAP Fault handling

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Protected by Anti-Spam ACP