Chris,
I'd just like to point out that there are two existing tools that may
have helped you our a lot: wget (often installed be default on many
Linuxes these days) and httping (which is not, but freely available and
has a simple "make" compile strategy).
I thought about those, but did not use
On 06.02.2009 14:46, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
André Warnier wrote:
Because the first part of this test had to be done by a non-specialist
customer on a workstation to which I did not have access, I ended up
writing a simple Perl script bas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
André Warnier wrote:
> Because the first part of this test had to be done by a non-specialist
> customer on a workstation to which I did not have access, I ended up
> writing a simple Perl script based on the integral LWP module, to better
> tr
Hi.
Just to anyone who contributed ideas to the issue originally mentioned,
thanks.
As a reminder, the problem was, on the one hand, entries like this one
in the mod_jk logfile :
[Mon Jan 19 15:02:52 2009] [6802:4416] [info]
ajp_process_callback::jk_ajp_common.c (1447): Writing to client a
Hi André,
On 28.01.2009 19:15, André Warnier wrote:
Caldarale, Charles R wrote:
From: André Warnier [mailto:a...@ice-sa.com]
Subject: And how about this mod_jk.log ?
I see mod_jk messages as listed below (from mod_jk to client, and from
mod_jk to Tomcat).
Any chance of getting network
Caldarale, Charles R wrote:
From: André Warnier [mailto:a...@ice-sa.com]
Subject: And how about this mod_jk.log ?
I see mod_jk messages as listed below (from mod_jk to client, and from
mod_jk to Tomcat).
Any chance of getting network traces for both the httpd-Tomcat and httpd-client
> From: André Warnier [mailto:a...@ice-sa.com]
> Subject: And how about this mod_jk.log ?
>
> I see mod_jk messages as listed below (from mod_jk to client, and from
> mod_jk to Tomcat).
Any chance of getting network traces for both the httpd-Tomcat and httpd-client
connections?
Hi.
I impolitely invaded/hijacked another thread before, was (justifiably)
ignored as a result, and stand duly chastised.
I apologise and this is a new posting to the same effect.
I have a case very similar to one previously mentioned, at a customer,
running under RHEL 5, with Apache 2.0.x, m