Support Article

Poor SOAP Connector performance



User is on Pega 7.2 and reported performance issues in Connect SOAP integrations. They are observing many PEGA0020 alerts in PegaRULES-ALERT logfile while calling a particular SOAP service.Tracer logs suggests that maximum time is being consumed in Step 14 of InvokeAxis2 activity.

Error Messages

Not Applicable

Steps to Reproduce

  1. Run a SOAP connector.

Root Cause

A defect or configuration issue in the operating environment is identified as root cause of this issue. The root cause of the delay is in the time it takes for the external system to complete the response. This is represented in the following PAL stats present in the PegaRULES-ALERT log. The 'pxConnectClientResponseElapsed' counter reflects the time it takes the external system to respond in milliseconds:



The reported issue is not related to defect or performance issue within the Pega server. Work with the provider of the external SOAP service to resolve this issue.


Published November 18, 2016 - Updated November 19, 2016

Have a question? Get answers now.

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