Thanks for your reply Mark! My sysadmin tells me just that we're
using "the defaults" for event_mpm. However we are still using the
BIO AJP connector:
<Connector port="8009" protocol="AJP/1.3" redirectPort="8443"
maxThreads="300" minSpareThreads="25"
maxSpareThreads="75" connectionTimeout="20000"/>
Is there a way I can tell from the Tomcat side when there is thread starvation?
--john
On Thu, Apr 27, 2017 at 12:34 PM, Mark Thomas <ma...@apache.org> wrote:
> On 27/04/17 17:47, John Cartwright - NOAA Federal wrote:
>> Hello All,
>>
>> We recently switched to Apache 2.4 and it's event mpm and are now
>> finding that some of our Tomcat 7 webapps are failing sporadically
>> when accessed via Apache - generally reporting 503s back to the
>> browser. The webapps work reliably when accessed directly from
>> Tomcat.
>>
>> We're using mod_jk for the connector - can someone please direct me to
>> resources on tuning Tomcat settings to match those of the Apache event
>> mpm or suggest what I should be tuning?
>
> Might you be using the BIO AJP connector on the Tomcat end? If so,
> switching to the NIO AJP connector should solve most if not all of the
> issues.
>
> (I suspect the problem is thread starvation although I can't find good
> docs on how the mod_jk connection pools work on the httpd end with the
> event worker.)
>
> Mark
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
