On 11/19/2014 09:27 PM, Lisa Woodring wrote:
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Lisa,
On 11/19/14 1:36 PM, Lisa Woodring wrote:
On Tue, Nov 18, 2014 at 2:43 PM, Christopher Schultz
ch...@christopherschultz.net wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256
Lisa,
On 11/18/14 11:52 AM, Lisa Woodring wrote:
We
Chris,
On Thu, Nov 20, 2014 at 3:16 PM, Christopher Schultz
ch...@christopherschultz.net wrote:
Lisa,
On 11/19/14 1:36 PM, Lisa Woodring wrote:
On Tue, Nov 18, 2014 at 2:43 PM, Christopher Schultz
ch...@christopherschultz.net wrote:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256
Lisa,
On Tue, Nov 18, 2014 at 2:26 PM, André Warnier a...@ice-sa.com 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 follow that up with an actual
On Tue, Nov 18, 2014 at 2:43 PM, Christopher Schultz
ch...@christopherschultz.net 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 working fine, except
Hi Lisa,
On 11/19/2014 07:28 PM, Lisa Woodring wrote:
On Wed, Nov 19, 2014 at 1:20 PM, Lisa Woodring lisa.woodr...@iglass.net wrote:
On Tue, Nov 18, 2014 at 2:26 PM, André Warnier a...@ice-sa.com wrote:
Lisa Woodring wrote:
...
In order to monitor
the availability of the HTTPS/AJP port
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 Tomcat boxes
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
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 follow that up with an actual request. This happens every 2
minutes.
...
This sounds like the perfect
-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 working fine, except that Tomcat is
keeping a high # of threads (in TIMED_WAITING state) -- and the CPU
has a
10 matches
Mail list logo
