Hi Uwe
Great news - it took us days to find this on our intranet. It wasn't helped
by the fact that only one of our call centre operators had the problem, and
she worked in a centre 400km away. It turned out that her desktop always had
a particular SAP application open plus one of ours.
I sure did learn a lot about cookies and useful Firefox plugins in the
process. If you don't already have it, WebDeveloper is great.
Regards
Ron
----- Original Message -----
From: "Poehner, Uwe" <uwe.poeh...@siemens.com>
To: "Ron McNulty" <rmcnu...@xtra.co.nz>; "Tomcat Users List"
<users@tomcat.apache.org>
Sent: Thursday, July 23, 2009 4:17 AM
Subject: AW: Wrong SessionID
Hi Ron,
thanks a lot! I'm pretty sure that's our problem and I already found some
SAP
J2EE Application Servers on our intranet with such a JSESSIONID
"(J2EE...)ID...End"
and (Cookie) Domain instead of Host configured (still 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 something very similar when a SAP server was incorrectly
configured to produce a JSESSIONID cookie that was global to the
organisation, rather than scoped to the server that produced it. The
"(J2EE13679500)" and "End" parts of the session ID look
suspiciously like
what I saw.
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 the
JSESSIONID cookie should
be configurable, but to my knowledge it is hard-coded.
If this is the problem, then it is your client's problem
(unless you are
seeing it from inside your intranet).
Regards
Ron
----- Original Message -----
From: "Poehner, Uwe" <uwe.poeh...@siemens.com>
To: <users@tomcat.apache.org>
Sent: 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 stickyness and our session.
Our environment (Hardware Loadbalancer -> 2 Apache Servers ->
2 Tomcat
Servers):
Solaris 10 8/07
Apache/2.2.6 with mod_proxy_ajp, mod_proxy_balancer, ...
Tomcat 5.5.23 with JDK 1.5.0_12-b04
Does anybody have an idea?
Thanks and Regards
Uwe
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
