Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Jetty SSL port does not close even maxIdleTime is reached


any chance of trying 9.1.4 or 9.2.0.M0?

It is very hard for us to find the time to support old versions in the open source forums.


On 2 April 2014 18:22, Bharti <bharti.goyal7@xxxxxxxxx> wrote:
I am not too much familiar with networking specifications. I will try to
provide information as much as I can.
I am using Linux OS.
hping command -
hping2 <ip of machine> -p 7443 -S -a <spoofing ip> -i u1000000

I have enabled jetty ssl port on server side.

After some analysis what I have observed is, If I use "SslSocketConnector"
instead of "SslSelectChannelConnector" then connections close properly after
maxIdleTime is reached.

Why is it not working with SslSelectChannelConnector?
Can I see any logs regarding this? How can I enable the logs?

View this message in context:
Sent from the Jetty User mailing list archive at
jetty-users mailing list

Greg Wilkins <gregw@xxxxxxxxxxx> HTTP, SPDY, Websocket server and client that scales  advice and support for jetty and cometd.

Back to the top