Re: [jetty-users] Session xxx is now immortal (maxInactiveInterval=-1)

[Silvio Bierman <sbierman@xxxxxxxxxxxxxxxxxx>]

I initially call setMaxInactiveInterval with 1800 as default value. In some cases this is changed afterwards (usually to a shorter lifetime) but most of the sessions will remain at 1800 until they are destroyed (or timeout, occasionaly).

But as I said, the message is logged immediately when the session is created so before I call setMaxInactiveInterval. If I call getInactiveInterval I do initially get a -1 value so the message is not false.

For some reasons my sessions are created as Highlanders by default, which is strange.

I should probably add that I use Jetty in embedded mode, though the embedding code has not changed and this message never came up with previous versions.

Cheers,

Silvio

On 03/22/2016 11:58 PM, Joakim Erdfelt wrote:

What value are you setting the setMaxInactiveInterval() to?

Joakim Erdfelt / joakim@xxxxxxxxxxx

On Tue, Mar 22, 2016 at 3:23 PM, Silvio Bierman <sbierman@xxxxxxxxxxxxxxxxxx> 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
jetty-users@xxxxxxxxxxx
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
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users