-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Kim,
Kim Albee wrote: > We are not doing URL rewriting with sessionid, it's saving as a > cookie. Okay. > Not sure how the sessionid is determined ... by Tomcat or Apache Tomcat generates the sessions and therefore their ids as well. > we have multiple servers and session sharing occurring with Tomcat, > so we are appending the server ID (worker.id) to the sessionid > variable, which Tomcat manages, but I'm not sure how Apache and/or > Tomcat determine the sessionid... do you know how that happens? How does your load balancer determine which server should get the request? Is it completely random, or does your lb know that about the server affinity of the session? Are you sure that session sharing is configured properly? Also, does this happen all of the time? Just in one particular place in your app? Or intermittently all over the place? If it's intermittently all over the place, then it might be that one of your servers is not configured properly while the rest are, and when you randomly end up using that misconfigured server, you drop your session. I would run your tests a few times and then post back with more details. For instance: 1. What is your lb configuration. If you are using Apache httpd with mod_jk, then post your mod_jk config. 2. When you lose the session, what are the circumstances? Which server: is it always the same one that loses the session? - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFrOiJ9CaO5/Lv0PARAv5IAJ9ykPWAFlHUWwuzmFwwjz/Qgp+NgwCffWRT xTpvRvo9sRMuTcqZqFW+V30= =lt7h -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
