You can use mod_jk2 sticky session (on by default) when load balancing with it, then
you can ignore Apache.
However the round robin distribution of users sessions in mod_jk1 and 2 doesn't work
properly at the moment for prefork Apache (1.x and 2.x in default configuration), see
this thread:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg97638.html
The downside of this approach is: if one Tomcat crashes, the Users on it will loose
their session (have to ask yourself if you can live with that).
The good thing is you don't need to change your application a bit.
Alternative is Tomcat 4 Session Clustering (Tomcat 5 will have this on board), see
http://cvs.apache.org/~fhanik/index.html
All your session attributes need to implement java.io.Serializable then.
However the author says
that running mod_jk in front of Tomcat causes a lot of session replication errors to
happen during load,
so it may not be production worthy for you.
Tomcat Users List [EMAIL PROTECTED] schrieb am 17.07.03 06:01:42:
Would anyone pls tell me how sessions are kept and passed between Apache
and Tomcat via jk2, e.g. whether it is completely transparent so that
when I write session related codes in Tomcat I can ignore Apache? What
about in a load balancing config (e.g. 1 Tomcat to 2 Apache, 1 Apache to
two Tomcat)?
Joseph Lam
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Simon Pabst
E-Mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
