right configured).
So I will continue to search for the evil one ...
Best Regards
Uwe
-Ursprüngliche Nachricht-
Von: Ron McNulty [mailto:rmcnu...@xtra.co.nz]
Gesendet: Mittwoch, 22. Juli 2009 11:09
An: Tomcat Users List
Betreff: Re: Wrong SessionID
Hi Uwe
I've seen so
rch for the evil one ...
Best Regards
Uwe
> -Ursprüngliche Nachricht-
> Von: Ron McNulty [mailto:rmcnu...@xtra.co.nz]
> Gesendet: Mittwoch, 22. Juli 2009 11:09
> An: Tomcat Users List
> Betreff: Re: Wrong SessionID
>
> Hi Uwe
>
> I've seen some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ron,
On 7/22/2009 5:09 AM, Ron McNulty wrote:
> The only fix was to correctly configure the offending server - there is
> nothing Tomcat can do. When a browser has two cookies with the same name
> in scope, the outcome is indeterminate. We found that
Ron McNulty wrote:
> The only fix was to correctly configure the offending server - there is
> nothing Tomcat can do. When a browser has two cookies with the same name
> in scope, the outcome is indeterminate. We found that the wider scoped
> cookie took precedence. I've often thought the name of t
ent: Wednesday, July 22, 2009 3:26 AM
Subject: Wrong SessionID
Hello,
our tomcat servers seem to produce very sporadically a wrong JsessionID -
instead of 58EB1F9C39278DBB72528A13EF026EFB.bsp01
we get (J2EE13679500)ID0574993050DB11991779031281660559End (without a
dot-jvmroute) so we lose
Hello,
our tomcat servers seem to produce very sporadically a wrong JsessionID -
instead of 58EB1F9C39278DBB72528A13EF026EFB.bsp01
we get (J2EE13679500)ID0574993050DB11991779031281660559End (without a
dot-jvmroute) so we lose stickyness and our session.
Our environment (Hardware Loadbalancer ->
