: RE: Tomcat clustering session attribute is changed without request
Hi,
Replication of the attributes is done by the cluster valve.
http://tomcat.apache.org/tomcat-6.0-doc/config/cluster-valve.html
If you manage to call that code from your own application, than you can do
what you want
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul,
On 10/24/2011 7:28 AM, Hodchenkov, Paul wrote:
2) AFAIK tomcat fires onSessionDestroyed event when some node in
cluster is stopped gracefully. However, in my environment I don't
observe such behavior.
Is that really what you want? Taking
Hi, thx for the response.
Yes, it's ok for me that sessions are not expired(session continue to live on
another node) and onsessiondestroyed is not called when one node is stopped.
The actual reason why i asked this question was that many folks complained that
tomcat always fired
.
So, is there any way to force the replication of HttpSession?
-Original Message-
From: Pid [mailto:p...@pidster.com]
Sent: Monday, October 24, 2011 4:08 PM
To: Tomcat Users List
Subject: Re: Tomcat clustering session attribute is changed without request
On 24/10/2011 14:05, Hodchenkov
List
Subject: Re: Tomcat clustering session attribute is changed without request
On 24/10/2011 14:05, Hodchenkov, Paul wrote:
Hi,
Thanks for the reply!
- What does 'stores session map in memory' actually mean?
It's ConcurrentMapString, HttpSession map which is filled by HttpListener.
I
Hi all,
I have configured tomcat 7 cluster by using [1] with DeltaManager and it works
fine.
However I have the following 2 questions:
1) My application stores session map in memory(admin can force logout of
any user and change some session attribute). Will this session attribute be
Op maandag, 24 oktober 2011 12:55 schreef Hodchenkov, Paul
paul.hodchen...@oxagile.com:
Hi all,
I have configured tomcat 7 cluster by using [1] with DeltaManager and it works
fine.
However I have the following 2 questions:
1) My application stores session map in
List
Subject: Re: Tomcat clustering session attribute is changed without request
Op maandag, 24 oktober 2011 12:55 schreef Hodchenkov, Paul
paul.hodchen...@oxagile.com:
Hi all,
I have configured tomcat 7 cluster by using [1] with DeltaManager and it
works fine.
However I have
On 24/10/2011 11:55, Hodchenkov, Paul wrote:
Hi all,
I have configured tomcat 7 cluster by using [1] with DeltaManager and it
works fine.
However I have the following 2 questions:
1) My application stores session map in memory(admin can force logout of
any user and change some
in this case?
What is the benefit of using JMX connection to access the session instead of
HttpListener in this case?
-Original Message-
From: Pid [mailto:p...@pidster.com]
Sent: Monday, October 24, 2011 3:59 PM
To: Tomcat Users List
Subject: Re: Tomcat clustering session attribute is changed
-Original Message-
From: Pid [mailto:p...@pidster.com]
Sent: Monday, October 24, 2011 3:59 PM
To: Tomcat Users List
Subject: Re: Tomcat clustering session attribute is changed without request
On 24/10/2011 11:55, Hodchenkov, Paul wrote:
Hi all,
I have configured tomcat 7 cluster
11 matches
Mail list logo