it will never be selected for any
practical purposes.
This patch has been tested extensivly in production use, and works
perfectly.
Paul Frieden
GOMEZ Henri wrote:
On Thu, Jun 14, 2001 at 10:28:47AM +0200, GOMEZ Henri wrote:
mod_jk support Apache 2.0
And TC 4.0 as preliminary support
Attached is a patch for the lb worker for mod_jk. Basically, it changes
the selection behavior slightly and adds some error and debugging
logging where we would find it useful.
The code uses two variables, lb_factor, and lb_value. lb_factor is the
numerical inverse (1/x) of what is entered
Rather than add fuel to the fire, I would like to summarize what I need
out of a servlet engine. Hopefully this will help the members of the PMC
make the correct decisions based off of what users need.
High Priority:
* Stability
We've been running Tomcat 3.1 without any problems for
and
Apache wouldn't be in the position it is in today.
Paul Frieden
PS: www.apache.org runs Apache 1.3.15-dev, and java.sun.com runs Apache
1.3.3.
GOMEZ Henri wrote:
It really scares me that you are the only person (as far as I
can tell) that
is seriously interested in maintaining and developing
In a load balanced environment, this is tricky with people behind a IP
randomizing proxy (like AOL). If you use all SSL, the load balancer can
track the SSL session ID across different IPs. If you use all non-SSL,
you can track with a cookie. You can use IP based sticky if the IP
stays the
to write up a section on it. Anybody interested?
Paul Frieden
On Wed, 6 Dec 2000, Bohm, Matt wrote:
I am a programmer in an environment that features load balancing on 3
production machines. Typically, requests to a given URL will be routed to
any of the three machines, depending on which
I was just flipping through this code because I did some changes to
CookieTools. To force a V0 cookie to be deleted properly, the time
should actually be set way in the past rather than the current time to
make it be deleted properly. I did it by checking if maxAge was 0 and
setting the expires
/Host
Host name="www.b.com"
Context path="" docBase="webapps/www.b.com" /
/Host
I don't think there is any reason why this wouldn't work with mod_jserv,
but I've only tested it with mod_jk and ajp12.
Is this documented in the new user guides? If not, it mi
is robust and fast Servlet 2.2/JSP
1.1.
Paul Frieden
Joseph Chiu wrote:
Matthew,
In my environment, I wanted to force all contexts to be in the root context.
So, my point is -- if you only need the root context (one context only!), my
kludge works. If you want root context and non-root
specifications. They made the way for Tomcat 4.0,
whatever code that may be. I don't think that code that works now should
be thrown away until the code that is intended to replace it is ready to
replace it.
Paul Frieden
On Sat, 4 Nov 2000 [EMAIL PROTECTED] wrote:
time explaining to people
10 matches
Mail list logo
