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 timeout issue while making a query

SA-32423

Summary



Making a query involving many classes causes a connect-soap timeout failure. User is required to change the "Response Timeout" value.

Error Messages



Step Status Info = ** SOAP service failed
Step Status = FAIL

pyStatusMsg com.pega.pegarules.pub.services.ResourceUnavailableException: SOAP service failed
pyStatusVal Fail:InternalReason


Steps to Reproduce



1. Create an activity.
2. Call Connect-SOAP rule in an activity
3. Expand and configure the Connect-SOAP step to create and configure the service name.
4. Observe that the newly created instance of Rule-Connect-SOAP does not allow to override timeout value.

Root Cause



A defect or configuration issue in the operating environment. A long running query which takes more than 30 seconds is failing.

Need to have an ability by means of which a "Response Timeout" value can be increased. Right now rule is not available and hence the user can not increase the timeout value.

Resolution



Apply HFix-31286.

Following are the steps to apply the hotfix:

1. Apply using the update manager.
2. Restart the server.
3. Try to configure the activity with the Connect-SOAP step.
4. Expand and configure the step to create and configure the service name.
5. Observe that the newly created instance of Rule-Connect-SOAP now allows to override timeout value.

Suggest Edit

Published April 25, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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