I have now been able to make it work on another minimalistic server
using the same worker.properties. It displays the runtime state. Now I
only have to find out what differs, that makes the status worker fail
getting runtime state. (It's a lot that differs so that may take a long
time :-/ )
Please open a bugzilla issue and attach the relevant parts of your
mod_jk config (jk directives from httpd.conf and workers.propertiers and
uriworkermap.orperties, if applicable).
Erik Melkersson schrieb:
Thanks for the info but unfortunately I don't think that is is case for
me. I surfed to a
N/A as a state means, that no requests have been sent to this worker for
some time. So mod_jk is not really able to tell you about the state of
the worker. It can only detect OK, ERROR etc. when it is sending
requests to the workers. No requests, no state.
A worker will be in state N/A
Thanks for the info but unfortunately I don't think that is is case for
me. I surfed to a mapped address and got pages back from the tomcat
trough the workers and still had N/A as state. I've also used it and got
an error message back (both tomcats blocked) but the state was still N/A.
As I
Does anyone recognize my problem about the runtime state that never is
displayed or did it work for you out-of-the-box?
Regards Erik Melkersson
Erik Melkersson wrote:
Hi!
I've got an apache (1.3.33) with mod_jk (1.2.21) connecting to two
tomcats (5.5.17) on other servers using a load
Hi!
I've got an apache (1.3.33) with mod_jk (1.2.21) connecting to two
tomcats (5.5.17) on other servers using a load balacer. (All running
debian.) I also have mounted a jkstatus on a directory.
My problem is that the jkstatus is never displaying the runtime state of
the workers. I always
