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 directly after starting Apache or if it
was in state OK, but didn't get any requests during a complete
maintenance interval. This is per default 60 seconds.
Regards,
Rainer
Erik Melkersson wrote:
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 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 get "N/A" in the "Balancer Members" under the
"Stat" column.
I've started it with working tomcats, tomcats blocked by a firewalls
and pointing towards localhost (that doesn't have any tomcats at all)
but all i get is "N/A".
...
worker.properties
*****************
worker.list=cms,jkstatus
worker.jkstatus.type=status
worker.cms.type=lb
worker.cms.balance_workers=cmsfront2,cmsfront3
worker.cmsfront2.type=ajp13
worker.cmsfront2.host=nnn.nnn.nnn.nnn
worker.cmsfront2.port=8009
worker.cmsfront2.lbfactor=1
worker.cmsfront2.redirect=cmsfront3
worker.cmsfront3.type=ajp13
worker.cmsfront3.host=nnn.nnn.nnn.nnn
worker.cmsfront3.port=8009
worker.cmsfront3.lbfactor=1
worker.cmsfront3.activation=disabled
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
