Hi, I am calling a SOAP Webservice from process model. If I get Connection

vbhardwaj

Certified Senior Developer

over 8 years ago

Hi,
I am calling a SOAP Webservice from process model. If I get Connection Reset exception from the Webservice, the process model gets paused. I am trying to catch the fault in fault variable in output tab of Call Webservice Smart Service. But no value is coming. How can I catch such a fault and handle it.

Have attached the process instance screenshot.
Details of fault ::

There is a problem with task “Call Web Service” in the process “testGetGlobalVendorList”. An error occurred while reading the WSDL 168.110.18.119:8080/.../Ryder_PO_GlobalVendorList_Orchestration_1_GlobalVendorListRcv_Port.asmx to create WSInvoker for the service {Ryder.com/}Ryder_PO_GlobalVendorList_Orchestration_1_GlobalVendorListRcv_Port and the endpoint Ryder_PO_GlobalVendorList_Orchestration_1_GlobalVendorListRcv_PortSoap. Communication with the remote server failed. Location: 168.110.18.119:8080/.../Ryder_P...

Discussion posts and replies are publicly visible

0 vbhardwaj
Certified Senior Developer
over 8 years ago

...O_GlobalVendorList_Orchestration_1_GlobalVendorListRcv_Port.asmx?WSDL; Details: Connection reset (APNX-1-4045-000)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 abhinavg over 8 years ago

when WS node is paused by exception, node output fault assignment will not work & fault will not be captured
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 neelimaj over 8 years ago

I think this can be handled in this way but not sure. Just try it.
1. Create a SAIL expression with webservicequery() forum.appian.com/.../Scripting_Functions.html function to make a call to web service. In this rule, handle the error by putting a check on it.
2. Use this rule in outputs of Scrip task in place of call web service node in process model.

Please check this and let us know if it solved your issue.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 danny.leo
Certified Associate Developer
over 8 years ago

Do you have nested CDTs - that the WS auto-creates? Nested CDTs violate Appian best practices...
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 james.franklin over 8 years ago

I use this app for testing WSDLs: WebServiceStudio (webservicestudio.codeplex.com/). However we experience issues with the WSDl node running into a similar state for no apparent reason so instead we nest it within a sub proc and run an exception from the subproc node instead. Hope this helps.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 vbhardwaj
Certified Senior Developer
over 8 years ago

Hi James,

Yes I am also calling WS from subprocess. When the fault occurs the subprocess as well as main process both are suspended. How can I catch the error in this case ?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 james.franklin over 8 years ago

I am not sure to be honest. My model allows for the process to resubmit the request to the WSDL (in the event it fails to respond) as it is unaffected by the WSDL node falling into exception. As you can see for yourself the problem appears to originate with the WSDL, apologies but beyond this I can't offer any further advice. In my experience not all faults can be captured from WSDL faults within the process.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel