Thanks Rainer, now I know where to direct the troubleshooting efforts.
Seems I have some networking issue.
On Thu, Oct 13, 2011 at 6:30 AM, Rainer Jung wrote:
> On 13.10.2011 06:16, Jorge Medina wrote:
>> I have Apache (2.2.20) in front of a single Tomcat (6.0.32) instance
>> using mod_jk (1.2.31
On 13.10.2011 06:16, Jorge Medina wrote:
> I have Apache (2.2.20) in front of a single Tomcat (6.0.32) instance
> using mod_jk (1.2.31) with the AJP protocol.
> I am getting errors like the sample below frequently (a few hundred
> times a day). The server does not have a heavy load, it serves abou
and another piece of information: Tomcat and Apache are running in the
same machine.
On Thu, Oct 13, 2011 at 12:24 AM, Jorge Medina
wrote:
> Correcting some information:
> I am using Apache 2.2.13, mod_jk 1.2.30, Tomcat 6.0.32
>
> On Thu, Oct 13, 2011 at 12:16 AM, Jorge Medina
> wrote:
>> I have
Correcting some information:
I am using Apache 2.2.13, mod_jk 1.2.30, Tomcat 6.0.32
On Thu, Oct 13, 2011 at 12:16 AM, Jorge Medina
wrote:
> I have Apache (2.2.20) in front of a single Tomcat (6.0.32) instance
> using mod_jk (1.2.31) with the AJP protocol.
> I am getting errors like the sample bel
I have Apache (2.2.20) in front of a single Tomcat (6.0.32) instance
using mod_jk (1.2.31) with the AJP protocol.
I am getting errors like the sample below frequently (a few hundred
times a day). The server does not have a heavy load, it serves about
150 req/minute and average response time of 200
