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: Max_HostConnections in DSS is ignored



Users complained that they are experiencing issues while running stress tests.

They are running many concurrent requests that all need to connect out via a Connect-SOAP call. The analyses shows that they are waiting a long time getting a connection.

Error Messages SOAP service failed
    at com.pegarules.generated.activity.ra_action_invokeaxis2_9dc5e2df6aa166e59ba37abbaaddd4b0.step15_circum0(

Steps to Reproduce

  1. Setup a SOAP endpoint that takes 1 minute to reply, for example on another Pega instance, but it could be on the same.
  2. Configure a Connect-SOAP to call this endpoint.
  3. Call it 10 times in parallel within 1 minute.
  4. See in the netstat results that only 2 sockets are opened to the endpoint. Default value of Max_HostConnections is 100, so even without DSS override this should demonstrate the issue. When the timeout of the Connect-SOAP is set to 2 minutes then a timeout occur. Another test might be to set the Max_HostConnection DSS to 1 and run a couple of parallel requests. Look at the netstat output to see 2 open sockets instead of 1.

Root Cause

A defect in Pegasystems’ code or rules : Default configuration settings are removed in prAxis 1.6.2 . So this doesn't work.


Apply HFix-29735.
Suggest Edit

Published January 5, 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