| Author |
Message
|
| wbintegrator |
 Posted: Sun Feb 14, 2010 5:35 am Post subject: Soap input problem |
 |
|
Voyager
Joined: 08 Feb 2006
Posts: 83
|
Hi.
i am devloping a message flow starting with a Soapinput node.
after devloping the flow during the tests i discovered
that when an exception occures it is not rolling back to the begginig of the flow, where i put my exception handler.
just to be clear, the exceptions that occur goes to the faliure terminals, but i want them to go back to the starting node's catch terminal where i connected my exception handler.
thanks. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Sun Feb 14, 2010 5:57 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
So have you checked out what happens if you do not wire the failure terminals of subsequent nodes? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| wbintegrator |
| Posted: Sun Feb 14, 2010 6:21 am Post subject: |
|
|
Voyager
Joined: 08 Feb 2006
Posts: 83
|
if i dont wire the faliure trminal the message is lost.
i wired the faliure terminal just to check that the exceptions are been created, i dont need the faliure terminals of the other nodes.
i want the catch terminal of the first node (Soapinput) to handle all the exceptions.
thanks. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Feb 14, 2010 7:33 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| wbintegrator wrote: |
if i dont wire the faliure trminal the message is lost.
i wired the faliure terminal just to check that the exceptions are been created, i dont need the faliure terminals of the other nodes.
i want the catch terminal of the first node (Soapinput) to handle all the exceptions.
thanks. |
Well have you researched under which conditions the message goes to the catch terminal? I believe you are trying to work against the product instead of with the product here...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| wbintegrator |
| Posted: Mon Feb 15, 2010 5:33 am Post subject: |
|
|
Voyager
Joined: 08 Feb 2006
Posts: 83
|
i know that when i woprk with MQ Input node in case of ann error during the flow, if the error terminals of the flow are not wired it is rolled back to the MQInput node and the treatment is done there (because i wired the catch terminal of the MQinput node to my exception handler).\
The mqinput node is working in transaction mode.
i want to know how i do this when using soapinput node
thanks. |
|
| Back to top |
|
|
| balaji83it |
| Posted: Wed Feb 17, 2010 12:14 am Post subject: |
|
|
Acolyte
Joined: 20 Jul 2007
Posts: 72
|
Hello,
Try connecting both failure and catch terminals of the SOAP Input node.
Also how are you putting the SOAP input node?
Are you dragging and dropping the wsdl and then select the option "expose as webservice" ?
or
Are you putting a SOAP Input node and providing wsdl.
I think the first would be a better way of doing it. It comes with various terminals connected.
Thanks
Konijeti Balaji. |
|
| Back to top |
|
|
| Herbert |
| Posted: Fri Feb 19, 2010 5:04 am Post subject: |
|
|
Centurion
Joined: 05 Dec 2006
Posts: 146
Location: Leersum, The Netherlands
|
| wbintegrator wrote: |
| i want the catch terminal of the first node (Soapinput) to handle all the exceptions. |
Assuming you did not select the option "send errors to failure terminal" (or named something like that, currently the online WMB infocenter gives me only German text, and my German is even worse then my English)
The error handing of SOAPInput node is indeed not as usual:
- Sometimes the request does not reach the flow at all ( with really bad client requests, for example not SOAP at all). I don't think this will happen in production with sofware as clients, but those human testers .....
- Sometimes it goes directly to the failure terminal, bypassing the Catch terminal. (looks like this is your scenario)
- A throw as last statement in the Catch Terminal does not activate the Failure terminal.
We ended up with putting the Error handling in a sublflow (logging and building a SOAP Fault response) and connected that subflow to both the Failure as the Catch termail. |
|
| Back to top |
|
|
|
|
