tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Gomez" <henri.go...@gmail.com>
Subject Re: mod_jk release preparation: ready for test
Date Sat, 16 Dec 2006 13:05:20 GMT
Good explanation since I wondering why the jkstatus didn't see my
JKMount directive.

In my case the jkstatus is defined in the httpd.conf (common) and the
JKMounts in all VHost.

It's a very common configuration since Web admins don't want to
redifine a jkstatus for each vhost.


>2006/12/16, Rainer Jung <rjung@apache.org>:
> Hi David,
>
> this message means, that no forwarding rules (=map) have been found for
> that worker. So no JkMount, mount attribute in workers.properties or
> uriworkermap.properties applies to that worker.
>
> Important: maps are associated to virtual hosts in apache. The status
> worker can only see those maps, that belong to the same virtual host, it
> has been called in. So if you add all your maps to a vhost for
> production use, and add a status worker on a separate vhost for admin
> use, this status worker will not be able to see the maps from the
> production vhost. If you want to inhertif maps from the global server to
> vhosts, you need to set JkMountCopy for the vhost. More about that in
> the updated Apache docs page (reference guide) and the new
> uriworkermap.properties page.
>
> Could that be the reason for the message?
>
> We might improve the situation concerning the status worker in the
> future, but making available all the maps to it will be a major
> refactoring in the jk code (for apache, IIS can already see all the maps).
>
> Regards,
>
> Rainer
>
> David Rees schrieb:
> > On 12/6/06, Rainer Jung <rjung@apache.org> wrote:
> >> - reworked status worker (see new docs page)
> >
> > On my status worker page, I get the message:
> >
> > Warning: No URI Mappings defined for <workername> !
> >
> > Otherwise, everything seems to work OK so far in my limited testing.
> >
> > -Dave
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: dev-help@tomcat.apache.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message