-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tamar,
On 6/28/2009 11:10 AM, Tamar Furman (tfurman) wrote:
> The problem starts when the second webapp is opened as well. In this
> case, on timeout the session does get destroyed but the new session that
> is created on a new http request still hold
Tamar Furman (tfurman) wrote:
Hello,
I have two webapps sharing the same tomcat session.
...
The problem starts when the second webapp is opened as well.
...
Well, I would suggest to just stop sharing the session between your two
webapps, no ?
Hello,
I have two webapps sharing the same tomcat session. When a session is
created I set the session timeout dynamically on my session listener
using: session.getSession().setMaxInactiveInterval(). When only the main
webapp is open the timeout works nicely: the session is destroyed on
timeout a
