Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
7 replies
Subscribers
5 subscribers
Views
3884 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Integrations
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...
OriginalPostID-166521
OriginalPostID-166521
Discussion posts and replies are publicly visible
Parents
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
Reply
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
Children
No Data