I just made a small change to my embedding code. I have a snippet in
there where I do (pardon the language):
val hsm =
getSessionHandler.getSessionManager.asInstanceOf[HashSessionManager]
hsm.setUsingCookies(false)
hsm.setSessionIdPathParameterName(ServletContainer.sessionIdName)
and now I added:
hsm.setMaxInactiveInterval(1800)
This solves the issue and the messages have disappeared. So it seems
that the HashSessionManager now uses -1 as its default session lifetime.
Sounds like a bug to me.
Cheers,
Silvio
On 03/22/2016 11:58 PM, Joakim Erdfelt wrote:
What value are you setting the setMaxInactiveInterval() to?
Joakim Erdfelt / [email protected] <mailto:[email protected]>
On Tue, Mar 22, 2016 at 3:23 PM, Silvio Bierman
<[email protected] <mailto:[email protected]>> wrote:
Hello all,
I just upgraded to jetty-9.3.8.v20160314 and now get these strange
WARN logging messages every time I create a sesion by calling
request.getSession(true). Immediately after this a call
setMaxInactiveInterval on the session to limit its lifetime but
the message is then already logged.
Why do I get this message and how can I get rid of it?
Cheers,
Silvio
_______________________________________________
jetty-users mailing list
[email protected] <mailto:[email protected]>
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users
_______________________________________________
jetty-users mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users
_______________________________________________
jetty-users mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users
