Re: [jetty-users] Jetty 8.0.0 - 8.0.4 not closing connections using Sele

[Jan Bartel <janb@xxxxxxxxxxx>]

Mathijs,

What OS is this running on? Seems like it might be one that does not
have a timeout for FIN_WAIT_2 in the tcp stack, so the sockets might be
building up and up until you reach the limit.

Is this problem seen with persistent connections? If so, have you
tried closing the connection on each request?

Finally, do you have any log output that mentions problems with the
endpoint/connection?

thanks
Jan


On 31 October 2011 02:49, Mathijs Vogelzang <mathijs@xxxxxxxxxxxxxx> wrote:
> Hi,
> I'm running an embedded jetty server which has fairly high numbers
> ofconnections from mobile phones, which oftensuddenly lose connections
> without properly shutting them down.I noticed that on my server, over
> time it's building up lots ofconnections that are in FIN_WAIT2 state.
> This was the casewith 8.0.0, and also with the latest version 8.0.4. I
> tried both withopenJDK 6 and Sun JDK 6 (all on a linux 64 bit
> machine).Using a thread dump, I see that jetty is
> maintainingSelectChannelEndPoint s for these hundreds of idle
> connections,even though I'm setting maxIdleTime to 15000 (i.e. 15
> seconds). Someof the _idleTimestamp values are hours old already,but
> the connection doesn't seem to be cleaned up.Is there some setting I'm
> overlooking or is this a bug in jetty?
> Best regards,Mathijs Vogelzang
> _______________________________________________
> jetty-users mailing list
> jetty-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jetty-users
>