Dnia 2013-01-04, pią o godzinie 14:31 +0100, Sylvain Guglielmi pisze: > At first, we had to face "ghost connections" (from users not properly > disconnecting). To solve that, I changed c2s.xml to have > <check> > <interval>600</interval> > <idle>0</idle> > <keepalive>600</keepalive> > </check> > So "unplugged" connections will be closed correctly after 10min. It > solved the problem. > .... > My problem is that I still can see the 500 established connections > (netstat -n | grep 'XXX.XXX.XXX.XXX'). Even if this "connection spam" > occurred yesterday (long enough for <keepalive> to do its job)
Are you sure this is a problem with jabberd, not your TCP stack configuration? It's usually the job of TCP layer to detect and close torn-down connections and using user level protocol layer keepalives to enforce this is just for convenience to the users, so they won't write to the vacuum (instead just one whitespace gets lost). If you are on Linux take a look at: https://www.linux.com/learn/docs/ldp/768-tcp-keepalive-howto http://www.speedguide.net/articles/linux-tweaking-121 -- Tomasz Sterna Instant Messaging Consultant : Open Source Developer http://tomasz.sterna.tv/ http://www.xiaoka.com/portfolio
