Question

2
Replies
249
Views
Close popover
Sreecharan Babu Challagundla (SREECHARAN)
Cognizant Technologies Solutions US
Pega Infra Build, Admin & Migration
Cognizant Technologies Solutions US
US
SREECHARAN Member since 2011 24 posts
Cognizant Technologies Solutions US
Posted: September 5, 2018
Last activity: September 6, 2018
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-connection-errors-many-tcp-sockets-closewait-state-red

System Administration
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.