Re: Using mod_jk in cluster environment responds HTTP 500

. Regards. Christopher Schultz-2 wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Rikslovein, > > On 11/15/2010 5:33 AM, rikslovein wrote: >> None of my tomcat is configured with HTTP connector. They are configured >> only for AJP. Does the jkmanager

Re: Using mod_jk in cluster environment responds HTTP 500

orker.hub1.host=localhost worker.hub1.type=ajp13 worker.hub1.lbfactor=1 #worker.hub1.redirect=hub0 Regards... awarnier wrote: > > rikslovein wrote: >> Thanks for the quick response Chris. >> >> Please find the details given below: >> >> Let me know if you

Re: Using mod_jk in cluster environment responds HTTP 500

Chris, Also one more information: None of my tomcat is configured with HTTP connector. They are configured only for AJP. Does the jkmanager requires this HTTP port? Any relation between the non-SSL HTTP connector and jkmanager? Regards. rikslovein wrote: > > Thanks for the quick re

Re: Using mod_jk in cluster environment responds HTTP 500

type=status worker.loadbal_hub_prod.type=lb worker.loadbal_hub_prod.balanced_workers=hub0,hub1 worker.loadbal_hub_prod.sticky_session=false Christopher Schultz-2 wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Rikslovein, > > On 11/12/2010 7:19 AM, riks

Using mod_jk in cluster environment responds HTTP 500

em is sometimes the client request does go to deactivated tomcat instance resulting in HTTP 500 error. I want the request to be redirected only to the active tomcat instance and not the deactivated one. Please suggest how can I do this. Regards, rikslovein -- View this message in context: http:/