Доброго дня Олеже, Наші пости спонукали пофіксати багу. Принаймі автор думає що пофіксав. Зараз фікс в проміжній версії. Через кілька днів буде у 7.6.RC0 а потім у 8.
Коли будете піднімати новий activemq інстанс можна буде спробувати jetty буз ngnix. Вдалого дня, Володя -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Greg Wilkins Sent: Monday, November 28, 2011 2:59 AM To: JETTY user mailing list Subject: Re: [jetty-users] Jetty 8.0.0 - 8.0.4 not closing connections using SelectChannelConnector I believe I've fixed this now in jetty-7.6 (RC0 will be out in days and fix will also be merged to 8). Jetty now resets the idle timeout when it expires (and does a shutdownOutput), and if it expires again, the connection is closed without waiting for a FIN. I have a test harness that check this happens if the client holds the connection open and does not respond with a FIN. But I don't have the ability to test for a connection that goes dark, so confirmation this resolves the real word problem would be great! https://bugs.eclipse.org/bugs/show_bug.cgi?id=364921 cheers On 28 November 2011 09:46, Greg Wilkins <[email protected]> wrote: > Since this has been reproduced against latest branch, I've opened an > issue to track this bug: > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=364921 > > I'm wondering if the issue is that Jetty has sent a FIN to close the > connection but never receives a FIN in response. The idle timeout > should catch this case and close, but there are some other issues with > idle, so we will investigate. > > please put any extra info you have on the issue. > _______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users _______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
