On Sep 20, 2012, at 6:12 PM, Django Radonich-Camp wrote:
thank you for the replies chris and dan.
chris:
1. upgrading apache is possible, but not easy (puppet manages the install).
2. unfortunately i have not figured out how to reproduce the problem. we
did extensive load testing on the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan,
On 9/21/12 5:00 PM, Daniel Mikusa wrote:
There are a few ways to [get a thread dump].
http://wiki.apache.org/tomcat/HowTo#How_do_I_obtain_a_thread_dump_of_my_running_webapp_.3F
- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2
On Sep 19, 2012, at 5:38 PM, Django Radonich-Camp wrote:
hello.
we are running an application on tomcat and experiencing intermittent
periods where the application is non-responsive and thus non-functional.
the general set up is apache and tomcat, with mod_proxy_ajp as the
connector
thank you for the replies chris and dan.
chris:
1. upgrading apache is possible, but not easy (puppet manages the install).
2. unfortunately i have not figured out how to reproduce the problem. we
did extensive load testing on the system prior to launch and not once did
we see this problem...
hello.
we are running an application on tomcat and experiencing intermittent
periods where the application is non-responsive and thus non-functional.
the general set up is apache and tomcat, with mod_proxy_ajp as the
connector (specific details and configs below).
during these events, the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Django,
On 9/19/12 5:38 PM, Django Radonich-Camp wrote:
apache: Apache/2.2.14
That's 9 revisions out of date. Any chance you can upgrade to 2.2.23
and re-test? Is it reliably reproducible?
- -chris
-BEGIN PGP SIGNATURE-
Version:
