Hi Bill
If you just want the problem to go away, then look for the attribute
request.registerRequests in
http://tomcat.apache.org/tomcat-5.5-doc/config/ajp.html . If that is set to
false, then there is no locking within the checkRequest method. You lose
that ability to get stats for the
Hi
I'm running tomcat 5.5.25 on debian sarge 32 bit linux (2.6.8 kernel)
with ~ 1.5GB ram on a pentium 4 2GHz
with a mysql db 5.0.27
I've got a configuration with apache mod_jk 1.2.25 balancing to 2
tomcats which are both running running on jdk 1.6.0_16 -Xmx=256M
periodically, generally at
Hi Chris,
So just to follow up on your post,
So, really, it's not that you want to load balance based upon IP
address... you really want to predictably choose a member of the server
farm based upon some knowledge of the client such that, regardless of
the domain name used, the initial request
Ben, Rainer,
That is an excellent idea, and would seem to be a very elegant
solution, I'll give it a shot.
Thank you both very much. I really appreciate it.
Cheers
Simon
-
To start a new topic, e-mail: users@tomcat.apache.org
Hi André,
You could do the authentication and SSO handling at the Apache level, and
set some partial domain cookie at that level, with some cross-domain
identifier (as long as the domains have a common part of course).
The browser will later send this cookie back with each request addressed
Hi Chris,
Wow, does that really work? That's a tremendously cool hack, if so!
It seems to, although it's not yet been tested in anger and there is
scope for dependancy issues if you navigate from one domain directly
to the another expecting a continous session experience.
What I mean is that
Hello,
I'm using jk 1.2.25 with tomcat 5.5.25 and apache 2.0 on one debian
box - 2.4.27-2-386 i686 GNU/Linux
I've set up 3 tomcat instances that receive requests from the jk
load balancer worker
I've implemented in the web application, a simple cross domain single
sign on (SSO) mechanism.
Hi Chris,
Thanks for the reply,
Simon,
Simon Papillon wrote:
| when there are
| several all servicing requests in a load balanced context, it doesn't
| work, because the session ids from different domains may be directed
| to different tomcat instances / containers, which then breaks
