tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lawrence Lamprecht <>
Subject mod_jk status code and loadbalancer monitoring
Date Fri, 22 May 2009 11:58:52 GMT
I found a really old entry from way back in 2005. Reading through a
trail of messages under the heading "Adding working dynamically with mod_jk status"

What I would very much appreciate is two things. I would like to know
where I can get some clear documents on the status codes for mod_jk.
The status codes appear in the mod_jk.log file in the following format.

[Wed May 20 06:27:47 2009] [21343:33088] [debug] jk_handler::mod_jk.c
(1969): Service finished with status=200 for worker=loadbalancer1

I have also seen other entries for status=302 etc.

I would like to understand what these status code mean or represent.

The second thing that I would like to see is, do you have any
information on monitoring the workers in the mod_jk config. I know
about the jkstatus function, but that is not very dynamic. It only
really reports errors if the wroker is called.

I had an issue where I took down on of the two workers in the
loadbalancer config, I saw the error that the first worker was no
longer available, but as soon as the second worker took over the work,
then the error was cleared and nothing more was reported.

I have had an idea, but seeing as I am not a programmer, I have no
idea how to achieve this, but I hope that someone else has also had
the same bright spark.

I was hoping that there was some application that did something
similar to what webalizer does with the access.log file for the apache
web server that could analyze the mod_jk.log file and dynamically
report the status of the workers as things happen. Something like a dashboard
to show what state the workers are in at any given time. When the log file
is rolling in debug mode, there is very much information that could be
used to report back on the worker status.

I hope that someone might have some good ideas.

Somehting that I have also thought about is possibly upgrading the mod_jk version that I am
running at the mo.
I have the following setup.

Server version: Apache/2.0.52
Server built:   Jun 29 2007 05:08:11
JK Version: 1.2.15

I get really confused with the different versions and compatibility, so could I keep the current
Apache version and only upgrade mod_jk,
Where would I find instauction on how to go about doing this.

Thanks in advnce
Lawrence Lamprecht

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message