-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jeffrey,
On 8/24/2011 9:59 AM, Jeffrey Janner wrote: > As Chris pointed out, it is mostly used by folks running with > "sticky-sessions" Actually, use of the jvmRoute with non-sticky sessions seems like an unnecessary step to me, since non-sticky sessions implies that you either have no sessions (and it doesn't matter at all) or you have replicated sessions where it doesn't matter which cluster member you reach. > but from what I've been able to tell, most folks set up their > clusters that way. It lessens the headaches. Practically speaking, clustering Tomcat instances means session replication, which (if you ask me) does not warrant session stickiness (though session replication does take some time... I don't know enough about TC's clustering to know whether race conditions are possible or probable). For my money, I'd go for sticky sessions and no replication at all. If you really need cluster-wide session access, look to other solutions (memcached, db-backed sessions, etc.). - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk5VBagACgkQ9CaO5/Lv0PBM7ACeOaqKmQRe3U1/55wvDmh/qQnG IJcAnjYfmb6SZJv2fdvHEMV8BFbzH0sr =nr5Z -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
