cedence. 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).
>
> Regar
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 ->
