Question

2
Replies
235
Views
SREECHARAN Member since 2011 21 posts
Cognizant Technologies Solutions US
Posted: 2 years ago
Last activity: 2 years 1 month ago
Closed

SOAP Endpoint URL - TCP Socket Connection CLOSE_WAIT

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.

Ref: https://community.pega.com/knowledgebase/articles/troubleshooting-soap-…

System Administration
Moderation Team has archived post
Share this page LinkedIn