Distributed session deleted on failover

From: <CBeck@xxx.com>
Date: Fri Sep 20 2002 - 18:54:09 PDT

Using Resin 2.1.2 EE on
1) RedHat 7.3 Sun JDK 1.4.0_01
and
2) Win2k Pro Sun JDK 1.4.0_01

Relevant section of resin.conf

          <srun id='s1' host='host1' port='6802'srun-index='1' />
          <srun id='s2' host='host2' port='6801'srun-index='2' />

Relevant section of web.xml

     <session-config>
          <session-max>4096</session-max>
          <session-timeout>120</session-timeout>
          <enable-cookies>true</enable-cookies>
          <enable-url-rewriting>true</enable-url-rewriting>
          <!-- <file-store>WEB-INF/sessions</file-store> -->
          <!-- the following entries are for distributed sessions -->
          <tcp-store />
          <always-save-session id='true' />
          <ignore-serialization-errors id='true' />
          <reuse-session-id id='false' />
     </session-config>

Apache 1.3.23 is running on host1 and caucho-status correctly indicates
up/down status of the srun servers as I flick them on and off.

I have tcp-ring sessions enabled. I see the session saved on my second
machine. The contents of the files are slightly different at the beginning
and the end.

When I shut down host1, the next request gets sent to host2, I call
request.getSession(false) and my distributed session is then invalidated
and erased.

Any ideas why?

--
-Chris Beck - Coradiant, Inc - Research & Development - +1.514.908.6314-
-- www.coradiant.com - Technical foresight driving Internet economics --
------- This email represents my opinion, not that of Coradiant. -------
All sentient beings are created unequal. The best society provides each
with equal opportunity to float at their own level.
-- The Gowachin Primary
Received on Fri 20 Sep 2002 18:54:09 -0700

This archive was generated by hypermail 2.1.8 : Thu Sep 28 2006 - 20:17:15 PDT