John,
On Fri, Apr 28, 2017 at 11:48 AM, Rainer Jung wrote:
> Am 27.04.2017 um 22:21 schrieb Mark Thomas:
>>
>> On 27/04/17 20:08, John Cartwright - NOAA Federal wrote:
>>>
>>> Thanks for your reply Mark! My sysadmin tells me just that we're
>>> using "the defaults" for event_mpm. However we are
Am 27.04.2017 um 22:21 schrieb Mark Thomas:
On 27/04/17 20:08, John Cartwright - NOAA Federal wrote:
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:
Is there a way I can tell from the Tomc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
John,
(Grr... my initial reply didn't go to the list)
On 4/27/17 12:47 PM, 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 fa
On 27/04/17 20:08, John Cartwright - NOAA Federal wrote:
> 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:
>
> maxThreads="300" minSpareThreads="25"
> maxSpareThreads="75"
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:
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 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
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_j
