Chris,
On Thu, Nov 20, 2014 at 3:16 PM, Christopher Schultz
wrote:
>
> Lisa,
>
> On 11/19/14 1:36 PM, Lisa Woodring wrote:
>> On Tue, Nov 18, 2014 at 2:43 PM, Christopher Schultz
>> wrote:
>>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256
>>>
&g
>> Actually, I received a little clarification on the monitoring software
>> (I didn't write it). What it's trying to test is that the AJP port
>> itself is actually accepting connections. With Apache in front in a
>> production system, it could forward the actual request to one of
>> several Tom
On Tue, Nov 18, 2014 at 2:43 PM, Christopher Schultz
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Lisa,
>
> On 11/18/14 11:52 AM, Lisa Woodring wrote:
>> We recently upgraded from Tomcat 6.0.29 to Tomcat 8.0.14.
>> Everything appears to be worki
On Wed, Nov 19, 2014 at 1:20 PM, Lisa Woodring wrote:
> On Tue, Nov 18, 2014 at 2:26 PM, André Warnier wrote:
>> Lisa Woodring wrote:
>> ...
>>> In order to monitor
>>> the availability of the HTTPS/AJP port (Apache-->Tomcat), our
>>> monitoring so
On Tue, Nov 18, 2014 at 2:26 PM, André Warnier wrote:
> Lisa Woodring wrote:
> ...
>> In order to monitor
>> the availability of the HTTPS/AJP port (Apache-->Tomcat), our
>> monitoring software opens a port to verify that this works -- but then
>> does not foll
We recently upgraded from Tomcat 6.0.29 to Tomcat 8.0.14. Everything
appears to be working fine, except that Tomcat is keeping a high # of
threads (in TIMED_WAITING state) -- and the CPU has a high load & low
idle time. We are currently running Tomcat8 on 2 internal test
machines, where we also m
If you are undeploying & redeploying a webapp during development (without
restarting Tomcat), this can/will happen. If you stop and restart Tomcat,
you should avoid the issue.
-Original Message-
From: Félix Pedrera García [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 20, 2005 9:19
