Support Article
Connect-SOAP connections to SOAP service are not released
SA-16145
Summary
A system administrator sees increased open connections from the Pega platform to an external SOAP service in a mainframe region that continue to accumulate and cause connection issues. When explicitly run, a JVM garbage collection in the Pega platform reduces the open connections count. However, this full garbage collection does not occur automatically and eventually these connections are exhausted.
System is running Pega 7.1.7 installed on Red Hat Linux and is using JRE 1.6.0_45.
JVM args configured are
-Xms8192m -Xmx8192m -XX:MaxPermSize=512m -XX:PermSize=128m
Error Messages
Not Applicable
Steps to Reproduce
- Run the Connect-SOAP service.
- Monitor the open connection count.
Root Cause
A defect or configuration issue in the operating environment In a non-production environment, the problem cannot be reproduced.
In a production environment, the Connect-SOAP call to an external SOAP service goes through a data power load balancer URL and the issue is not reproduced if it is a direct call.
Resolution
Perform the following local-change:
- Set the HTTP protocol version as 1.0 in the Connect-SOAP record, the Advanced tab.
- Check the data power and firewall settings.
Published January 31, 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.