Bill Barker wrote:
Remy Maucherat wrote:
Hi,
- I'll add a thread pool similar to the one in Tomcat 4.0, as an
optional policy to the current one; the idea is that it's very dumb, and
could be more stable in some environments (that RH 9 thing ...), but is
not as efficient as the current one; I'll do some benchmarks to see if
for a single CPU computer there's any difference between the two, and I
propose that whichever is the fastest for that use case becomes the
default one (with a preference for the TC 4.0 one in case of a tie, as
it's simpler)
I'm a bit confused - what happened with the thread pool and how did we
end up with 2 ? I missed this change.
There was no change yet. I was proposing (re)introducing a more
conventional policy as an option (where I would just copy code from TC
4.1). At least, I'll do it to see without committing anything to see how
it compares.
- I think conf/jk2.properties should go, since we can have arbitrary
properties on the Connector element, and additionally, it has an
extremely confusing name; any comments on that ?
+1 :-)
It will make the Connector element in server.xml really hideous, and
restrict component names to be valid XML attribute names (e.g.
channelSocket.localhost:8009 is a no-no :). Other than that, I don't see a
problem.
I'm ok to keep the file if it's the only way, but it needs at least to
be renamed. Doesn't having a file restrict the AJP connector to
one-per-server ? (or did I miss something ?)
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
