Thanks for the replies. Yes, I decided to go with mod_jk rather than mod_proxy because there is more experience with mod_jk at our company. I've now got the system nearly fully configured for ssh, failover, etc. Thanks for the notes on jkmanager. I've also got that working as well. Very happy with the configuration at the moment. On Sun, Sep 2, 2012 at 8:39 PM, Igor Cicimov <icicimov@xxxxxxxxx> wrote: > On Sun, Sep 2, 2012 at 3:29 PM, Daniel Ruggeri <DRuggeri@xxxxxxxxxxx> wrote: >> >> On 8/31/2012 6:08 PM, Ed Young wrote: >> >> I now need to get the urls for the /admin/jkmanager or >> /balancer-manager working. Currently they are yielding 404. >> >> >> I didn't see this in your configuration, but you have to enable the >> balancer manager explicitly: >> >> <Location /balancer-manager> >> SetHandler balancer-manager >> Order deny,allow >> Deny from all >> Allow from 192.168 >> </Location> >> >> -- >> Daniel Ruggeri > > > Not if using mod_jk and although not specifically mentioned by the OP I > assume that's the path he has chosen for the failover/balancing. So the > mod_proxy_balancer statements should have been removed from the apache > config since you can use one module or the other (meaning mod_jk or > mod_balancer) but not both of them together. > > The manager will be accessible via following setting in mod_jk: > > JkMount /jkmanager/* jkstatus > > so the OP needs to create another worker named jkstatus of type status in > the worker.properties file. This is described in more details in the Apache > Tomcat Connector Reference Guide, workers.properties section. > > Igor -- - Ed --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|