Re: [jetty-users] Session timeout

I should also have added that you should upgrade to the latest jetty-9.4, which is jetty-9.4.6. From the look of some of those debug statements you're on a slightly older version. Jan On 6 September 2017 at 10:55, Jan Bartel wrote: > John, > > As you can see on your log

Re: [jetty-users] Session timeout

John, As you can see on your log trace, each session contains a timer that expires when the session maxInactiveInterval is reached. When the timer expires, that session is queued for attention by the scavenger. By default the scavenger thread only runs once every 10mins, so it is timing

Re: [jetty-users] Stream closed warning for JSP files, only when accessing from IE

Hi Jan, Many thanks for the tip. We were able to figure out the problem, once we understood why the PrintWriter was getting closed. Turns out we had a mobile detection within the JSP that was forwarding the request to another JSP page. This was happening early enough so that it was not

Re: [jetty-users] Session timeout

On 05/09/2017 18:18, John English wrote: Later tests showed that a second request made between 5 and 10 minutes later also triggers sessionDestroyed(), and that a request is needed to trigger the call to sessionDestroyed() if the DEBUG flag is not turned on; with no DEBUG parameter and no

Re: [jetty-users] Session timeout

On 05/09/2017 05:10, Jan Bartel wrote: John, Can you provide the rest of your jetty configuration as regards sessions. Also, please run your app with debug turned on for sessions (-Dorg.eclipse.jetty.server.session.LEVEL=DEBUG) and post that. You should see some debug info about the maximum

Re: [jetty-users] Stream closed warning for JSP files, only when accessing from IE

Pankaj, Hhhm, looks like the PrintWriter has already been closed. Can you put a breakpoint in org.eclipse.jetty.server.ResponseWriter.close() and see who is calling it? Also, are you using HttpServletResponseWrappers? If so, make sure that if you have overridden getWriter() that you have also