I tracked down the source of the hang I was seeing
running Tomcat 3.3's internal test with Apache 2.0.
It turns out the native/Apache2.0 mod_jk.c code:
/* Use per/thread pool ( or context ) to reuse the
endpoint. It's a bit faster, but I don't know
how to deal with load
On Tue, 7 May 2002, Larry Isaacs wrote:
#ifdef REUSE_WORKER
I think it would be best to programmatically determine if
tpool is usable to fetch a thread unique endpoint, and
do something appropriate if it is not. Before I go digging
into Apache 2.0 code, I would appreciate any suggestions
