Have you considered storing your session objects to database?
Mario Winterer <[EMAIL PROTECTED]> wrote:Hi!
Is it really necessary to hold all active session objects in a global
variable? I can't imagine a situation that would require this!
Tex
Jagadeesha T wrote:
>Thanks for respondin
Hi!
Is it really necessary to hold all active session objects in a global
variable? I can't imagine a situation that would require this!
Tex
Jagadeesha T wrote:
Thanks for responding.
To manage session between an apllication and web servers. Is there any way to
get that worked in clustered envio
uster will obviously have its own
classloaders. The standard clustering only shares the sessions that are stored
within the standard session manager in tomcat.
-Original Message-
From: Shey Rab Pawo [mailto:[EMAIL PROTECTED]
Sent: 08 February 2005 17:44
To: Tomcat Users List
Subject: R
Thanks for responding.
To manage session between an apllication and web servers. Is there any way to
get that worked in clustered enviornment?
Thanks
Jagga
"Dale, Matt" <[EMAIL PROTECTED]> wrote:
Yes it will, this won't work accross a cluster. You need to use the regular
session manager.
Could you explain why this won't work across a cluster? Thanks.
On Tue, 8 Feb 2005 17:28:59 -, Dale, Matt <[EMAIL PROTECTED]> wrote:
>
> Yes it will, this won't work accross a cluster.
> Hi all,
> I' am storing session objects in a SINGLEON class object to keep all
> active sessions
Yes it will, this won't work accross a cluster. You need to use the regular
session manager.
Is there any reason why you put the sessions in a singleton?
Ta
Matt
-Original Message-
From: Jagadeesha T [mailto:[EMAIL PROTECTED]
Sent: 08 February 2005 17:25
To: tomcat-user@jakarta.apache.
> From: Jagadeesha T [mailto:[EMAIL PROTECTED]
> I' am storing session objects in a SINGLEON class
> object to keep all active sessions. Does it give any problems
> in clustered enviornment since singleton is a static referrence.
Yes. Singletons are one-per-classloader. Classloaders are
