RE: Clustering failing over with Tomcat 6.0.16
I created a simple session variable test and it seems to be working. I must have a problem with how I am using it in my application. I will look for in the framework will send my findings. But at this time, its not a tomcat issue.. -Original Message- From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 13, 2008 12:30 PM To: Tomcat Users List Subject: Re: Clustering failing over with Tomcat 6.0.16 It resyncs upon startup. can you provide a simple test case for us, the more you provide, the faster we can get you an answer Filip Gupta, Sharad wrote: I have tried different time periods, it still is reproducible ... -Original Message- From: Angus Mezick [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 13, 2008 8:49 AM To: Tomcat Users List Subject: RE: Clustering failing over with Tomcat 6.0.16 Does it take time for nodeA to resync the sessions after it comes back up? Could Sharad be shutting down nodeB too early? --Angus Mezick -Original Message- From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] Sent: Monday, August 11, 2008 11:07 PM To: Tomcat Users List Subject: Re: Clustering failing over with Tomcat 6.0.16 nope, it should work both ways Gupta, Sharad wrote: Hi, I have a cluster of Tomcat 6.0.16 using DeltaManager. Session replication works fine, failover works fine for the first time. That is, the first time I failover from, lets say, nodeA to nodeB, my session is carried over the user continues with the existing logged in session without being asked to log back in. But the problem happens when nodeA comes backup nodeB needs to be shutdown. The session information is somehow, not carried over as my app asks me to relogin at that point in time. Is this a desired behaviour with DeltaManager? Thanks - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Clustering failing over with Tomcat 6.0.16
Does it take time for nodeA to resync the sessions after it comes back up? Could Sharad be shutting down nodeB too early? --Angus Mezick -Original Message- From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] Sent: Monday, August 11, 2008 11:07 PM To: Tomcat Users List Subject: Re: Clustering failing over with Tomcat 6.0.16 nope, it should work both ways Gupta, Sharad wrote: Hi, I have a cluster of Tomcat 6.0.16 using DeltaManager. Session replication works fine, failover works fine for the first time. That is, the first time I failover from, lets say, nodeA to nodeB, my session is carried over the user continues with the existing logged in session without being asked to log back in. But the problem happens when nodeA comes backup nodeB needs to be shutdown. The session information is somehow, not carried over as my app asks me to relogin at that point in time. Is this a desired behaviour with DeltaManager? Thanks - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Clustering failing over with Tomcat 6.0.16
I have tried different time periods, it still is reproducible ... -Original Message- From: Angus Mezick [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 13, 2008 8:49 AM To: Tomcat Users List Subject: RE: Clustering failing over with Tomcat 6.0.16 Does it take time for nodeA to resync the sessions after it comes back up? Could Sharad be shutting down nodeB too early? --Angus Mezick -Original Message- From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] Sent: Monday, August 11, 2008 11:07 PM To: Tomcat Users List Subject: Re: Clustering failing over with Tomcat 6.0.16 nope, it should work both ways Gupta, Sharad wrote: Hi, I have a cluster of Tomcat 6.0.16 using DeltaManager. Session replication works fine, failover works fine for the first time. That is, the first time I failover from, lets say, nodeA to nodeB, my session is carried over the user continues with the existing logged in session without being asked to log back in. But the problem happens when nodeA comes backup nodeB needs to be shutdown. The session information is somehow, not carried over as my app asks me to relogin at that point in time. Is this a desired behaviour with DeltaManager? Thanks - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Clustering failing over with Tomcat 6.0.16
It resyncs upon startup. can you provide a simple test case for us, the more you provide, the faster we can get you an answer Filip Gupta, Sharad wrote: I have tried different time periods, it still is reproducible ... -Original Message- From: Angus Mezick [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 13, 2008 8:49 AM To: Tomcat Users List Subject: RE: Clustering failing over with Tomcat 6.0.16 Does it take time for nodeA to resync the sessions after it comes back up? Could Sharad be shutting down nodeB too early? --Angus Mezick -Original Message- From: Filip Hanik - Dev Lists [mailto:[EMAIL PROTECTED] Sent: Monday, August 11, 2008 11:07 PM To: Tomcat Users List Subject: Re: Clustering failing over with Tomcat 6.0.16 nope, it should work both ways Gupta, Sharad wrote: Hi, I have a cluster of Tomcat 6.0.16 using DeltaManager. Session replication works fine, failover works fine for the first time. That is, the first time I failover from, lets say, nodeA to nodeB, my session is carried over the user continues with the existing logged in session without being asked to log back in. But the problem happens when nodeA comes backup nodeB needs to be shutdown. The session information is somehow, not carried over as my app asks me to relogin at that point in time. Is this a desired behaviour with DeltaManager? Thanks - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Clustering failing over with Tomcat 6.0.16
Hi, I have a cluster of Tomcat 6.0.16 using DeltaManager. Session replication works fine, failover works fine for the first time. That is, the first time I failover from, lets say, nodeA to nodeB, my session is carried over the user continues with the existing logged in session without being asked to log back in. But the problem happens when nodeA comes backup nodeB needs to be shutdown. The session information is somehow, not carried over as my app asks me to relogin at that point in time. Is this a desired behaviour with DeltaManager? Thanks
Re: Clustering failing over with Tomcat 6.0.16
nope, it should work both ways Gupta, Sharad wrote: Hi, I have a cluster of Tomcat 6.0.16 using DeltaManager. Session replication works fine, failover works fine for the first time. That is, the first time I failover from, lets say, nodeA to nodeB, my session is carried over the user continues with the existing logged in session without being asked to log back in. But the problem happens when nodeA comes backup nodeB needs to be shutdown. The session information is somehow, not carried over as my app asks me to relogin at that point in time. Is this a desired behaviour with DeltaManager? Thanks - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
