[Exist-development] Too many CLOSE_WAIT status in jetty

[Masoud V. <ma...@gm...>]

Hi all,
I had configured eXist-db to be behind of an other web server, at the
first, I configured it to proxying eXist-db behind an Apache web server;
all of things were good until I understood that the performance has
decreased very much, though the memory and cpu usage were normal! by
netstat command I noticed that too many connections are in CLOSE_WAIT
status and not terminated!! I searched very much and imagined the bug is
for apache! therefore I change Apache with Nginx web server! but the
problem not solved!! and after 3 or 4 days, too many connections will be
stays on CLOSE_WAIT still! the solution is restart the eXist process
(java)! (right now, 214 connections are in close_wait status!)
so, I guessing the problem may be from jetty or jvm, therefore I searched
around this issue and found following link (and some other links
<https://www.google.com/?gws_rd=ssl#q=jetty+CLOSE_WAIT+>):
http://stackoverflow.com/questions/23644090/too-many-close-wait-in-jetty-9-0-3
http://stackoverflow.com/questions/28875406/why-am-i-seeing-lots-of-sockets-in-close-wait-status-when-webservice-stops-worki
...
now, i want to help for solve this issue! what is the solution?
(in the first link, writer is mentioned to use closeIdleConnections(0)
function; is it helpful? Where is it being?)

Thanks