I'm currently struggling with the same problem, did you manage to solve it?
If you attempt to retry the stalled component through adminui, it will work. Am i correct?
If so, you can test the following approach.
1. drag a blank component (e.g a decision point)
2. connect a line between the exception of the Web Service Invoke operation to the decision point.
3. Choose java.io.IOException from the eeception drop down.
4. again connect the decision point back to the web service invoke component. (i mean a looping)
This approach was working fine with me.
Please see the attached image shows my routing.
PS: After a couple of days, I tested without looping and it seems to be working. So I removed the loop now.
Thanks for the answer Nith!
Regrettably, are not it a possible solution for my problem, because there is no error catched by Livecycle. Sniffing TCP packets shows the connection reset, but there is no crash in Livecycle.
I keep on digging.
1 person found this helpful
Try trapping the java.net.SocketTimeoutException off of the Invoke Web Service operation.
You may also want to trap java.lang.Exception.
I have had success intercepting these errors, incrementing an error loop counter and returning to the Invoke Web Service operation.
I don't encounter the errors often, but usually the first attempt resets the connection, and the second try works.
I'll be grateful if you can show me how did to solve this problem.
Coz i have a lot of process who are stuck on calling web service