Maybe it is just a question of perspective.
An Apache httpd VirtualHost is not a separate entity, like a child process or a
thread.
It is just a "personality" which any Apache child temporarily takes, during the processing
of one single request.
At the next request processed by this same Apache
My bad, if I put only
JkMount /jkmanager/* jkstatus
in the VirtualHost it works but it doesn't allow any other jk setting to be
put inside. So I have the rest of the mod_jk settings in the httpd.conf
making them globally available.
Still wonder why would only jkmanager behave this way?
Ig
Hi all,
I have tomcat 6.0.26 running on Soalaris 10 and Apache 2.2.15 in front of it
with mod_jk 1.2.31 on the same host. I can't get the jkmanager page back
from mod_jk and this is my relevant configuration:
1) /usr/local/apache2/conf/httpd.conf
JkWorkersFile conf/workers.properties
J
