Hi,
for completeness: the issue seems to have been resolved.
The problems were apparently caused by a misconfigured
router between the webservers and the appservers.
Am Mittwoch, 14. Oktober 2009 schrieb Mark Thomas:
>
> > Any idea how to gain more information?
>
> Jk debug logs
> wireshark
> com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Conrad,
On 10/15/2009 9:44 AM, conrad-tomcat.users.2...@tivano.de wrote:
>> If you could post your httpd configuration for your worker/prefork stuff
>> AND your mod_jk configuration, it might be helpful.
>
> ===workers.properties===
All that looks o
Hi,
Am Mittwoch, 14. Oktober 2009 schrieb Christopher Schultz:
>
> Although those threads say "runnable", they're really blocked at the OS
> level waiting to receive data from the mod_jk connector. These threads
> are actually idle, waiting for requests from httpd to come through the
> pipe.
>
> Y
On Wed, Oct 14, 2009 at 6:15 PM, Mark Thomas wrote:
> Have you tried
> JkOptions +DisableReuse
>
>
And if that solves the problem setup connection timeout .
http://tomcat.apache.org/connectors-doc/generic_howto/timeouts.html
Evgeny
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter,
On 10/14/2009 10:48 AM, conrad-tomcat.users.2...@tivano.de wrote:
> Currently, they're using Tomcat-5.5.26 on SUN's jdk 1.5.0_10 (64 bit)
> and mod_jk 1.2.28. Over the years, we have seen the same situation since
> before Tomcat-5.5.12.
>
> Mo
conrad-tomcat.users.2...@tivano.de wrote:
> Hi,
>
> our customer is running a cluster of tomcat servlet engines. On these,
> our web application is running. The basic setup is
>
> Loadbalancer <---> Apache 1.3.x with mod_jk <---> Tomcat
>
> with 2-3 Apache servers and >30 Tomcat instances bundle
Hi,
our customer is running a cluster of tomcat servlet engines. On these,
our web application is running. The basic setup is
Loadbalancer <---> Apache 1.3.x with mod_jk <---> Tomcat
with 2-3 Apache servers and >30 Tomcat instances bundled into clusters
of 3-5 instances each. Apache + Tomcat ser
