edit bug #13 by person #0

[BugRat Mail System <to...@cortexity.com>]

Bug description modified:
   Description changed from:
    > I have two servers with identical servlets on both doing load balancing
(1 JVM per server). For this example consider A1 to be servlet A running
on server 1 and so on, B2 to be servlet B on server 2 etc.

<code>

A1 -> set cookie to (say) abc=20
B2 -> reads from the cookie. gets abc=20. correct.
C2 -> deletes the cookie (setMaxAge to 0)
C2 -> sets a new cookie abc=30
C2 -> reads from the cookie. gets abc=30. correct.
B1 -> reads from the cookie. gets abc=20 <---------------- bug.
B2 -> reads form the cookie. gets abc=30. correct.

</code>

I'm using mod_jserv.so to do the load balancing. using netscape 4.73 to
access the servlets and tomcat 3.2b2 with blackdown JDK 1.2.2FCS on
redhat linux 6.2 kernel 2.2.16-3.

I cant offer any insight into whats causing it...AFAIK this behaviour was
not present in 3.1 and changing the JDK doesnt help. it only occurs with
load balancing and not with the regular non load balanced operation. It
doesnt affect me any more since i've worked around it and dont care
either way....but it shouldnt really be present anyway. 
Any comments/insights ?
   To:
    > I have two servers with identical servlets on both doing load balancing
(1 JVM per server). For this example consider A1 to be servlet A running
on server 1 and so on, B2 to be servlet B on server 2 etc.

<code>
<pre>

A1 -> set cookie to (say) abc=20
B2 -> reads from the cookie. gets abc=20. correct.
C2 -> deletes the cookie (setMaxAge to 0)
C2 -> sets a new cookie abc=30
C2 -> reads from the cookie. gets abc=30. correct.
B1 -> reads from the cookie. gets abc=20 <---------------- bug.
B2 -> reads form the cookie. gets abc=30. correct.

</pre>
</code>

I'm using mod_jserv.so to do the load balancing. using netscape 4.73 to
access the servlets and tomcat 3.2b2 with blackdown JDK 1.2.2FCS on
redhat linux 6.2 kernel 2.2.16-3.

I cant offer any insight into whats causing it...AFAIK this behaviour was
not present in 3.1 and changing the JDK doesnt help. it only occurs with
load balancing and not with the regular non load balanced operation. It
doesnt affect me any more since i've worked around it and dont care
either way....but it shouldnt really be present anyway. 
Any comments/insights ?
Reproduce description modified:
   Description changed from:
    > 
   To:
    > See Description

Work around description modified:
   Description changed from:
    > 
   To:
    > Recommend anyone using cookies to treat them as fixed
values as cookie deleting/value changing is IMHO not reliable 100% of the
time in tomcat 3.2+. Setting cooklies works 100% of the time.