Re: Tomcat clustering session attribute is changed without request

2011-10-27 Thread Hodchenkov, Paul
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 onsessiondestro

Re: Tomcat clustering session attribute is changed without request

2011-10-27 Thread Christopher Schultz
-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? Takin

RE: Tomcat clustering session attribute is changed without request

2011-10-27 Thread Hodchenkov, Paul
t; 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, Paul wrote: > > Hi, > > Thanks for th

RE: Tomcat clustering session attribute is changed without request

2011-10-25 Thread Ronald Klop (Mailing List)
It means you don't have to jump through hoops to access something that is already accessible elsewhere. p > -Original Message- > From: Pid [mailto:p...@pidster.com] > Sent: Monday, October 24, 2011 3:59 PM > To: Tomcat Users List > Subject: Re: Tomcat clusteri

RE: Tomcat clustering session attribute is changed without request

2011-10-25 Thread Hodchenkov, Paul
fine. 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, Hodch

Re: Tomcat clustering session attribute is changed without request

2011-10-24 Thread Pid
s already accessible elsewhere. p > -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, Ho

RE: Tomcat clustering session attribute is changed without request

2011-10-24 Thread Hodchenkov, Paul
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 with

Re: Tomcat clustering session attribute is changed without request

2011-10-24 Thread Pid
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

RE: Tomcat clustering session attribute is changed without request

2011-10-24 Thread Hodchenkov, Paul
4, 2011 2:20 PM To: Tomcat Users List Subject: Re: Tomcat clustering session attribute is changed without request Op maandag, 24 oktober 2011 12:55 schreef "Hodchenkov, Paul" : > > > > Hi all, > I have configured tomcat 7 cluster by using [1] with DeltaManager and

Re: Tomcat clustering session attribute is changed without request

2011-10-24 Thread Ronald Klop (Mailing List)
Op maandag, 24 oktober 2011 12:55 schreef "Hodchenkov, Paul" : 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

Tomcat clustering session attribute is changed without request

2011-10-24 Thread Hodchenkov, Paul
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 replic