Support Article
com.pega.apache.commons.httpclient.ConnectionPoolTimeoutExceptio
SA-29419
Summary
The user is seeing "com.pega.apache.commons.httpclient.ConnectionPoolTimeoutException: Timeout waiting for connection"
Issue happens for SOAP connection and failing due to timeout. User needs to restart server to resolve this issue to reset the connection pool, but the issue reoccurs after a few hours of activity.
Error Messages
Caused by: com.pega.apache.commons.httpclient.ConnectionPoolTimeoutException: Timeout waiting for connection
at com.pega.apache.commons.httpclient.MultiThreadedHttpConnectionManager.doGetConnection(MultiThreadedHttpConnectionManager.java:491)
at com.pega.apache.commons.httpclient.MultiThreadedHttpConnectionManager.getConnectionWithTimeout(MultiThreadedHttpConnectionManager.java:395)
at com.pega.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:153)
at com.pega.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
at com.pega.apache.axis2.transport.http.AbstractHTTPSender.executeMethod(AbstractHTTPSender.java:629)
at com.pega.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:193)
at com.pega.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
at com.pega.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:411)
at com.pega.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:233)
at com.pega.apache.axis2.engine.AxisEngine.send(AxisEngine.java:445)
at com.pega.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:406)
at com.pega.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
at com.pega.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
at com.pegarules.generated.activity.ra_action_invokeaxis2_4054e98ba19df03aff55083d242bbf9d.step14_circum0(ra_action_invokeaxis2_4054e98ba19df03aff55083d242bbf9d.java:3910)
at com.pegarules.generated.activity.ra_action_invokeaxis2_4054e98ba19df03aff55083d242bbf9d.perform(ra_action_invokeaxis2_4054e98ba19df03aff55083d242bbf9d.java:291)
Steps to Reproduce
1. Restart the JVM.
2. Let the environment execute Connect-SOAP calls for 3 - 4 hours after the JVM restarts.
Root Cause
A defect in Pegasystems’ code or rules. The Axis2_Max_Connections and the Axis2_Max_HostConnections setting they’ve setup in the DSS is not getting picked up in the INIT (Step5) lookup logic, leaving the default on 2.
Resolution
Apply HFix-29961.
Published November 2, 2016 - 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.