nection pooler, which was required because the application
specifies the password which DBCP could not handle.)
Regards,
Anthony
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker
Sent: Tuesday, January 15, 2008 12:09 PM
To: users@tomcat.apache.org
Subject: Re:
OTECTED] On Behalf Of Bill Barker
> Sent: Tuesday, January 15, 2008 12:09 PM
> To: users@tomcat.apache.org
> Subject: Re: Effect of MaxThreads
>
> Yes, but the way that the default, non-APR, AJP/1.3 Connector works,
> connections generally will stay open tying up the correspondi
ssage
news:[EMAIL PROTECTED]
> From: Berglas, Anthony [mailto:[EMAIL PROTECTED]
> Subject: Effect of MaxThreads
>
> Tomcat connectors provide maxThreads parameter to throttle
> the number of concurrent transactions. But what actually
> happens when this number is exceeded?
It
> From: Berglas, Anthony [mailto:[EMAIL PROTECTED]
> Subject: Effect of MaxThreads
>
> Tomcat connectors provide maxThreads parameter to throttle
> the number of concurrent transactions. But what actually
> happens when this number is exceeded?
It's in the doc:
http://t
Tomcat connectors provide maxThreads parameter to throttle the number of
concurrent transactions. But what actually happens when this number is
exceeded? Are additional requests queued, or are they simply bounced?
We have Apache in front of Tomcat (for dubious reasons). Where is the
best place
