Keep Server Online
If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.
or
A donation makes a contribution towards the costs, the time and effort that's going in this site and building.
Thank You! Steffen
Your donations will help to keep this site alive and well, and continuing building binaries. Apache Lounge is not sponsored.
| |
|
 Topic: Apache 2.2.3/mod_jk 1.2.19/Tomcat 5.5.20 problem |
|
| Author |
|
hatfield
Joined: 04 Jan 2007
Posts: 2
|
 Posted: Thu 04 Jan '07 15:48 Post subject: Apache 2.2.3/mod_jk 1.2.19/Tomcat 5.5.20 problem |
 |
|
We recently attempted to upgrade from 2.0.58+jk2 to 2.2.3+jk1.2.19 (mod_proxy_ajp wouldnt function properly due to our complex environment) with a very strange problem showing up.
We had reports of a situation where user A in application A issued a call to a servlet and receiving back the response from a call from user B in system B. We have never seen this before and the problem went away after rolling back to 2.0+jk2.
Our environment consists of 3 win2003 boxes behind a layer 4 switch with apache and tomcat (clustered for session replication) on all 3. Each apache is configured to talk to all 3 tomcats for failover. Each tomcat hosts over a dozen webapps, two of which run under their own virtualhost and the remaining run under a 3rd virtualhost. Sticky sessions are used.
Our assumption is something may have been broken between apache and tomcat but I cant find anything here, google, or in the changelogs for mod_jk 1.2.20.
I'd like to get to 2.2.3 to take advantage of the cleaner log rotation (currently using cronolog to rotate daily with 2.0).
Thanks. |
|
| Back to top |
|
hatfield
Joined: 04 Jan 2007
Posts: 2
|
|
| Back to top |
|
|
|
|
|
|
