Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Connect-SOAP failsTransport error: 302 Error: Moved Temporarily

SA-12499

Summary



Connect-SOAP calls fail because of response code 302 from calling service. This is reproducible in lower environment as well.

com.pega.apache.axis2.AxisFault: Transport error: 302 Error: Moved Temporarily
at com.pega.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:311)


Error Messages



2015-07-13 08:00:02,674 [fault (self-tuning)'] [TABTHREAD4] [ AccessGroup] ( transport.http.HTTPSender) INFO <host>|<IP>|Rule-Connect-SOAP.PegaSample-.AttachDocument User - Unable to sendViaPost to url[http://<hostname>/webservice/V1?WSDL]

com.pega.apache.axis2.AxisFault: Transport error: 302 Error: Moved Temporarily
at com.pega.apache.axis2.transport.http.HTTPSender.handleResponse(HTTPSender.java:311)
at com.pega.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:200)
at com.pega.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:76)

Steps to Reproduce

1. Call connect-SOAP with file attachments.
2. Check the response code; notice it is '302' instead of '200'.


Root Cause



The root cause of this problem is defect/misconfiguration in the operating environment. 

Resolution



Issue was reproduced outside of Pega using SOAP UI tool. Pega/SOAP UI call when made directly to the external server works, when routed through proxy or webserver it returned 302 and the call did not make it to the external service at all. Engage the webserver admin to address this environment issue.

Published July 30, 2015 - Updated October 8, 2020

Was this useful?

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us