Why Connect SOAP Throws Error With Status Code 503 During Test Connection with Pega 7.4
I have a Service SOAP rule that works in Pega 7.2 but when I unit test in Pega 7.4 it returns 503 status error (503Service Unavailable).
I found on PDN https://community1.pega.com/community/pega-support/question/why-connect-soap-throws-error-status-code-405-during-test-connection
But that is a solution for error 405 Method Not Allowed is to update the Method name which does not apply here. Pega 7.2 uses Java 7 and Pega 7.4 uses Java 8, but that is the only difference that I see. (See screen shot) Any suggestions?
Pegasystems Inc.
FR
Hello,
Well looks like the server is unavailable or too busy. You can maybe trace the Test connectivity execution to analyze a bit more
Pegasystems Inc.
IN
can you enable the debug for below logger and attach the log here.
Rule_Obj_Activity.ValidateInfrastructure.Rule_Connect_SOAP.Action
maku sure you tested the service from SOAPUI
Pegasystems Inc.
US