Re: SPAM?: Re: Tomcat replication Unable to receive message through TCP channel

2004-01-16 Thread jean-philippe . belanger
YOU'RE KIDDING ME!

sorry for the caps but I just lost a day of work for a stupid server out 
of time! :P

Thanks btw!

Jean-Philippe Bélanger
CGI
Apu Shah wrote:

check the dates on both machines. i think (filip please clarify if i'm
wrong) if one machine is out of sync with the other by an interval equal
or greater than the session timeout, the sessions will expire on the
receiving end.


 

Ok I really have no idea why this ain't working.
Same clustering version on both cluster. The first one works A1.. the
second invalidates all my sessions
Only difference between the two clusters are that the 2nd one is a
multi-ip server (3 adresses on the same eth). But the hostname is
pointing to the main eth0 address.
any idea?

Jean-Philippe Bélanger
CGI


Filip Hanik wrote:

   

yikes :)
I fixed this one two days ago, download 5.0.18 and let me know if the
problem persists.
Filip



 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
   



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: SPAM?: Re: Tomcat replication Unable to receive message through TCP channel

2004-01-16 Thread Filip Hanik
awesome catch Apu
I will add this to my to do list, so that replication is independent of
server out of synch time

Filip

- Original Message -
From: [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Sent: Friday, January 16, 2004 10:51 AM
Subject: Re: SPAM?: Re: Tomcat replication Unable to receive message through
TCP channel


 YOU'RE KIDDING ME!

 sorry for the caps but I just lost a day of work for a stupid server out
 of time! :P

 Thanks btw!

 Jean-Philippe Bélanger
 CGI


 Apu Shah wrote:

 check the dates on both machines. i think (filip please clarify if i'm
 wrong) if one machine is out of sync with the other by an interval equal
 or greater than the session timeout, the sessions will expire on the
 receiving end.
 
 
 
 
 
 Ok I really have no idea why this ain't working.
 Same clustering version on both cluster. The first one works A1.. the
 second invalidates all my sessions
 
 Only difference between the two clusters are that the 2nd one is a
 multi-ip server (3 adresses on the same eth). But the hostname is
 pointing to the main eth0 address.
 
 any idea?
 
 Jean-Philippe Bélanger
 CGI
 
 
 
 Filip Hanik wrote:
 
 
 
 yikes :)
 I fixed this one two days ago, download 5.0.18 and let me know if the
 problem persists.
 
 Filip
 
 
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]