On 05.04.2011 22:44, Anthony J. Biacco wrote:
FYI, I have this tentatively working with mod_unique_id by doing:
Apache config:
RequestHeader set UNIQUE_ID %{UNIQUE_ID}e
JkEnvVar UNIQUE_ID
Tomcat accesslogvalve pattern:
%{UNIQUE_ID}i
I might use it like this, I might not. They
apache_host:unique_id
Thanks,
-Tony
> -Original Message-
> From: Anthony J. Biacco [mailto:abia...@formatdynamics.com]
> Sent: Tuesday, April 05, 2011 1:55 PM
> To: Tomcat Users List
> Subject: RE: tomcat and apache log entry correlation with mod_jk
>
> Nothing yet, was in resea
Nothing yet, was in research and spitball mode, but am currently looking at
mod_unique_id
-Tony
> -Original Message-
> From: Christopher Schultz [mailto:ch...@christopherschultz.net]
> Sent: Tuesday, April 05, 2011 1:08 PM
> To: Tomcat Users List
> Subject: Re: tomcat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Anthony,
On 4/5/2011 2:21 PM, Anthony J. Biacco wrote:
> I'm using apache 2.0.17, tomcat 6.0.28 (and soon tomcat 7) with mod_jk
> 1.2.28 on CentOS 5.5
> I'd like to put a unique identifier in the tomcat request log and the
> apache request log so that
I'm using apache 2.0.17, tomcat 6.0.28 (and soon tomcat 7) with mod_jk
1.2.28 on CentOS 5.5
I'd like to put a unique identifier in the tomcat request log and the
apache request log so that I can match up log entries between the two.
Is there any way to do this with mod_jk, maybe with JkEnvVar? And
