Support Article
Connect-SOAP: Max_HostConnections in DSS is ignored
SA-29249
Summary
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
com.pega.pegarules.pub.services.RemoteApplicationException: SOAP service failed
at com.pegarules.generated.activity.ra_action_invokeaxis2_9dc5e2df6aa166e59ba37abbaaddd4b0.step15_circum0(ra_action_invokeaxis2_9dc5e2df6aa166e59ba37abbaaddd4b0.java:4004)
Steps to Reproduce
- Setup a SOAP endpoint that takes 1 minute to reply, for example on another Pega instance, but it could be on the same.
- Configure a Connect-SOAP to call this endpoint.
- Call it 10 times in parallel within 1 minute.
- 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.
Resolution
Apply HFix-29735.
Published January 5, 2017 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.