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 response time exceeds 300 seconds



CONNECT-SOAP exceeds 300 seconds even though response timeout is 20 seconds.

ResourceUnavailableException is thrown instead of SocketTimeoutException.

Error Messages

Exception ResourceUnavailableException is thrown

Steps to Reproduce

This issue is not reproducible at will.

Invoke the SOAP connector through a workflow.

If the endpoint has some intermittent connectivity issue then the SOAP connector level timeout is not taking effect.

The connector waits for a response and ignores the rule level timeout.

Root Cause

A defect or configuration issue in the operating environment.

The issue is not reproducible at will so actual root cause is not known.


As a preventative and probable solution, update the invokeaxis2 activity and add the following codes:

Step 7:

Search the line “options.setTimeOutInMilliSeconds(timeout)” and comment out and add the following lines:


//directly set the timeout properties
options.setProperty(com.pega.apache.axis2.transport.http.HTTPConstants.SO_TIMEOUT, new Integer(timeout));
options.setProperty(com.pega.apache.axis2.transport.http.HTTPConstants.CONNECTION_TIMEOUT, new Integer(timeout));

In step 11:

Adding the following 3 lines:

int timeout = myStepPage.getProperty("pySOAPTimeout").toInteger();

After the line:

options.setProperty(com.pega.apache.axis2.transport.http.HTTPConstants.REUSE_HTTP_CLIENT, "true");”

Published November 8, 2017 - 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.

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