ResourceUnavailableException occurs when Connect-SOAP is run
ResourceUnavailableException occurs when Connect-SOAP is run.
[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
java.net.SocketTimeoutException: Read timed out
at java.net.SocketInputStream.socketRead0(Native Method)
Steps to Reproduce
Invoke the Connect-SOAP.
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.
Published February 13, 2018 - Updated October 8, 2020
Was this useful?
0% found this useful
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.