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

Performance issues with Soap Services



Performance issues were noticed, and the browser hung occasionally.

Example SOAP exceeded 1000ms
RULE-CONNECT-SOAP ORG-INT-<ServiceCategoryName>-<ServiceName>Service- INVOKESERVICE #20140203T191636.309 GMT has exceeded the threshold of  1,000 ms: 16,782 ms;pxConnectOutMapReqElapsed=29;pxConnectClientResponseElapsed=15544;pxConnectInMapReqElapsed=342;

Error Messages

Not Applicable

Steps to Reproduce

Run process to invoke Connect SOAP call.

Root Cause

The root cause of this problem is due to slow performance in custom application external services.


Review Connect-SOAP rules and endpoint services for proper SLA timeframes.

Published March 14, 2016 - Updated December 2, 2021

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