Support Article
ResourceUnavailableException occurs when Connect-SOAP is run
SA-48400
Summary
ResourceUnavailableException occurs when Connect-SOAP is run.
Error Messages
[WebContainer : 39] [TABTHREAD0] [ ] [my_app:xx.yy.zz] (internal.mgmt.Executable) ERROR URL|IP|Rule-Connect-SOAP.ABC-Int-XYZService.Wech UserID - Exception
com.pega.pegarules.pub.services.ResourceUnavailableException: SOAP service failed
.
.
.
Caused by:
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:165)
at java.net.SocketInputStream.read(SocketInputStream.java:134)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:247)
at java.io.BufferedInputStream.read(BufferedInputStream.java:266)
at com.pega.apache.commons.httpclient.HttpParser.readRawLine(HttpParser.java:78)
Steps to Reproduce
Invoke the Connect-SOAP.
ROOT CAUSE
A defect in Pegasystems’ code or rules. From the log messages, the Connect-SOAP did not receive any response from the client.
This was caused due to the authentication timing out, or the wire was cut (virtually or even physically, although the latter have additional implications), by a network component like a proxy, a firewall, or a WAN-router. Theoretically, the read could also time out because the end-point was overloaded and therefore unable to respond in time.
Resolution
Apply HFix-29961.
Published February 13, 2018 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.