Thanks to Charles and Edmond for replying.
The problem was actually in my code. Tomcat destroyed the session, but
when calling sessionDestroyed()
(before the session is completely destroyed), a user bean that was
expected was already null.
The bottom line: session-timeout does work properly fo
> From: Oren Livne [mailto:[EMAIL PROTECTED]
> Subject: Problems with tomcat session timeout on linux
>
> The problem: some times users log in and then close their
> browser window (at least I assume so), but tomcat never
> destroys their session. The session-timeout parameter is
> set to 30 in
Well, I must admit, I run Ubuntu myself and I have noticed on a few
occasions (after multiple netbeans builds) that the session doesn't get
destroyed in a timely manner sometimes. So it is possible that there is an
issue but it happens for me very rearly, I don't know whether this is an
issue that
Hi Edmond,
Thanks for your feedback. I am implementing a session listener and a
session event
with custom sessionCreated() and sessionDestroyed(). Indeed, I thought
that the timeout
is all I needed, but the point is ... that it doesn't work properly for
me on linux. It does on windows.
Thank
You may want to look into SessionListener/Session event Listener. I am not
sure what the issue is with regards to the timeout, setting timeout to 30
means the session should expire in 30 minutes. The timeout is really all you
should need as far as wanting to prevent idle sessions, after all that i
