oldrich-s commented on issue #5495: URL: https://github.com/apache/couchdb/issues/5495#issuecomment-2765870930
Just to clarify, what happens is that any application (NodeJS, curl) makes a connection to CouchDB 3.X. When the HTTP connection is closed, the application (curl) keeps the TCP connection open for reuse. In one second, we make a new curl HTTP request. Therefore, curl shall reuse the old TCP connection and not create a new one. This works when making a HTTP connection against CouchDB 2.X or any other app such as dummy NodeJS http server or httpbin website etc. There we observe that TCP connection is being reused and the number of used ports does not increase. When we make connection against CouchDB 3.X, the TCP connection is never reused and a new connection is created every time. Therefore we observe an increasing number of TCP connections in TIME_WAIT state. We observe it on Windows Server machines and on Windows 12 desktop. I have a suspicion that CouchDB "closes" the HTTP connection in such a way that prevents the client app to reuse the TCP port and is therefore forced to create a new TCP connection every time. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@couchdb.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
