ril 22, 2001 1:30 PM
> To: [EMAIL PROTECTED]
> Subject: RE: 3.2.2b3 mod_jk gets stuck in readFully
>
>
> If 100 is a constraint for the pool size, it should be stated in
> the Tomcat
> User's manual, since there it is explained how to increase the
> pool, but no
>
Thanks for your help, Marc.
Would it be possible to log a message to tomcat.log if the thread pool gets
exhausted? I believe the default Apache installation calls for 256 children,
so busy sites are going to run into this. A log message suggesting to
increase max_threads could save a lot of agg
o: Marc Saegesser; [EMAIL PROTECTED]
> > Subject: RE: 3.2.2b3 mod_jk gets stuck in readFully
> >
> >
> > After quite a bit of struggle, I think I found out what is going on. The
> > problem is that the default configuration of Tomcat does not have enough
> > threa
. See if this fixes your problem better than using
SimpleTcpConnector.
> -Original Message-
> From: Pogo Com [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, April 21, 2001 5:39 PM
> To: Marc Saegesser; [EMAIL PROTECTED]
> Subject: RE: 3.2.2b3 mod_jk gets stuck in readFully
&g
After quite a bit of struggle, I think I found out what is going on. The
problem is that the default configuration of Tomcat does not have enough
threads in its thread pool for the default configuration of Apache. This
issue would only be apparent if many Apache children were in use.
The result
s a show stopper bug for 3.2.2.
> -Original Message-
> From: Pogo Com [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, April 19, 2001 7:19 PM
> To: [EMAIL PROTECTED]
> Subject: 3.2.2b3 mod_jk gets stuck in readFully
>
>
> I've been testing Tomcat 3.2.2b3 and
I've been testing Tomcat 3.2.2b3 and Apache 1.3 on Solaris, connected with
mod_jk. Things are generally working, but there is a serious problem that
occurs under load.
The problem is that certain Apache children get stuck talking to Tomcat. The
children are always requesting JSP pages. Using t
