tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sudip pattanayak <getsudi...@yahoo.co.in>
Subject Re: Tomcats Sessions not getting released
Date Wed, 11 Feb 2009 05:21:13 GMT
Hi Chirstopher,
 
Thanks for responding.
 
Actually our design structure is such that we allow just one session for any user.
 
So when if a user is logged in any other system or he has not logged off the previous instance,
and then again he tries to login then we tell the user that your session is already active,
do you want forcefully loggoff or not, if he says yes then the the previous sessions are identified
and we give a call to the normal logoff function.
 
But the problem comes when sometime this forcefull logoff fails. The session the user is logged
in previously is not released when the forcefull logoff is called and therfore the function
fails and  the subsequent login is not allowed.
 
In the logoff function we call the session ID is identified for the previous login of the
user and at the same time value unbound is called so that the user is releases from the earlier
session.
 
Please let me know if you need any more info......
 
Thanks,
Sudip

--- On Wed, 11/2/09, Christopher Schultz <chris@christopherschultz.net> wrote:

From: Christopher Schultz <chris@christopherschultz.net>
Subject: Re: Tomcats Sessions not getting released
To: "Tomcat Users List" <users@tomcat.apache.org>
Date: Wednesday, 11 February, 2009, 1:37 AM

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sudip,

On 2/10/2009 2:36 AM, sudip pattanayak wrote:
> We have an implementation where by we call the value unbound to
> release sessions for any users.

Could you explain this in more detail?

> For any user which does not logoff from the previous session we
> logoff the user forcefully for the next session he tries to login.

How do you force a logoff? Do you store all created sessions somewhere?
If so, how and where do you store them?

> But there are couple of instances not consistent though that the
> sessions instances remains active and the forceful log-off
> fails.....So far my understanding and the what the logs suggests that
> the Tomcat does not release the previous sessions....

Again, how do you actually perform the "forceful log-off"?

- -chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkmR3nUACgkQ9CaO5/Lv0PAvcACbBTZyzjveiLjBeqVDLCR8GFkR
ZcQAn1PjKnIN5Rcn/jWufrL8nIXQKSnI
=u9CY
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org




      Add more friends to your messenger and enjoy! Go to http://messenger.yahoo.com/invite/
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message