Getting ConnectionPoolTimeoutException from logs
SummaryWhen attempting to load test while invoking SOAP web services, repeated ConnectionPoolTimeoutExceptions are thrown in logs.
com.pega.pegarules.pub.services.ResourceUnavailableException: SOAP service failed
Caused by: com.pega.apache.commons.httpclient.ConnectionPoolTimeoutException: Timeout waiting for connection
Steps to ReproduceInvoke web service during performance tests.
Root CauseDue to load test the pool was being exhausted during the runs.
ResolutionAxis2 defaults MaxTotalConnections and MaxHostConnections to 20 and 2 respectively. PRPC defaults them to 1000 and 100 respectively. Given that the timeout is happening while acquiring a connection, user must increase the number of connection and max host connections:
This can be done through the DSS settings below:
a) Purpose : Axis2_Max_ConnectionsRuleset : Pega-IntegrationEngine
Value : 1000b) Purpose : Axis2_Max_HostConnectionsRuleset : Pega-IntegrationEngine
Value : 100
Published July 27, 2016 - Updated October 8, 2020