Recently we observed in our development env is slowing down when checked server it has nearly 1000 TCP connects in "CLOSE_WAIT" state ( with an SOAP End point URL).. this happening on one service out of 20. There is an article published by #PegaGCS for v6.2SP2, i hope this issue might fixed in later versions, but we seeing in Pega v7.3.1 either.
If adding "Axis2_Max_HostConnections to 100 and for Axis2_Max_Connections to 1000" to DSS is best practice why weren't this in Installation document.
Let us know if this setting required on v7.3.1. Why pega unable to close TCP socket associated with SOAP connection.
Yes, you would have to use those DSS. This is fixed in Pega 7.4. If you need the hotfix in Pega 7.3.1, log a SR with GCS support to get the Hfix-38277 ported.
Pega is supposed to be keeping ONE connection manager per node around for SOAP. It has a pool on which we set a limit of 1000 (we can configure it via the "Axis2_Max_Connections" Dynamic System Setting).
When a Connection Manager has "too many" connections, it will close idle ones in order to allow for new connnections.
The connections are in CLOSE_WAIT state because neither side (client/server) told the other to close the connection (via use of the Connection header). One of the internal classes of Pega were missing hash functions which leads to this duplication of objects.