|[jetty-users] Jetty ssl connections do not close after MaxIdleTime with SslSelectChannelConnector|
Hi, I am running a client which sends SYN and ACK packets at Jetty SSL port at a rate of 10 packets/sec. In jetty-ssl.xml, MaxIdleTime parameter is set to 300000 sec (5 min) and NIO connector (SslSelectChannelConnector) is configured. Flooding is stopped after 2 minutes. By that time, approximately 1200 connections get created. After 10 minutes it was observed that even though the connections were idle for more than 5 minutes, they remain in "Established" state. As per the specified configurations, these connections should get closed after MaxIdleTime (5 min) is reached. But, when the same scenario is executed with Blocking connector (SslSocketConnector), connections are getting closed after MaxIdleTime. Same happens for non ssl port as well. Is it a known issue with Jetty ssl implementation? Please reply asap. Any help regarding the same would be appreciated. Regards, Bharti -- View this message in context: http://jetty.4.x6.nabble.com/Jetty-ssl-connections-do-not-close-after-MaxIdleTime-with-SslSelectChannelConnector-tp4962415.html Sent from the Jetty User mailing list archive at Nabble.com.
Back to the top