Re: Using mod_jk in cluster environment responds HTTP 500

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rikslovein, On 11/17/2010 12:14 AM, rikslovein wrote: > Thanks for your help and your responses once again. I now solved the > problem. The problem was with the jkmanager URL I was using in the code. Glad to hear you found the problem. > I think th

Re: Using mod_jk in cluster environment responds HTTP 500

Chris & all, Thanks for your help and your responses once again. I now solved the problem. The problem was with the jkmanager URL I was using in the code. I think there is a change in URL attributes from older version. The current version uses vwa, vwr and vwf (which was coded as wa, wr & wf re

Re: Using mod_jk in cluster environment responds HTTP 500

-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 requires this HTTP port? Do you mean the "manager" webapp that comes with Tomcat? No, i

Re: Using mod_jk in cluster environment responds HTTP 500

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rikslovein, On 11/15/2010 12:47 AM, rikslovein wrote: > Server.xml > enableLookups="false" redirectPort="8443" protocol="AJP/1.3" /> Is redirectPort="8443" correct for your environment? This has nothing to do with your HTTP 500 problems, but it's wo

RE: Using mod_jk in cluster environment responds HTTP 500

> > > > > worker.list=loadbal_hub_prod,jkstatus,hub0,hub1 > > > > This is wrong. If the workers are already balanced (by the loadbal_hub_prod > balancer), > then they should not be separately listed in worker.list. > Correct : > worker.list=loadbal_hub_prod,jkstatus > Well, assuming he doesn't

Re: Using mod_jk in cluster environment responds HTTP 500

awarnier, Thanks for your response. I changed this and still it didn't solve my problem. The request are still reaching to the server which I made down using jkmanager. Here's the updated workers.proeprties: worker.list=loadbal_hub_prod,jkstatus worker.loadbal_hub_prod.type=lb worker.loadbal_hub

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 response Chr

Re: Using mod_jk in cluster environment responds HTTP 500

rikslovein wrote: Thanks for the quick response Chris. Please find the details given below: Let me know if you need more information. Thanks & regards... Server.xml enableLookups="false" redirectPort="8443" protocol="AJP/1.3" /> workers.properties: workers.tomcat_home=/opt/webhost/DWH-Tomc

Re: Using mod_jk in cluster environment responds HTTP 500

Thanks for the quick response Chris. Please find the details given below: Let me know if you need more information. Thanks & regards... Server.xml workers.properties: workers.tomcat_home=/opt/webhost/DWH-Tomcat-Inst/tomcat5.5.23 workers.java_home=/usr/lib/jvm/java-1.5.0 ps=/ worker.list=lo

Re: Using mod_jk in cluster environment responds HTTP 500

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rikslovein, On 11/12/2010 7:19 AM, rikslovein wrote: > I've one apache and two tomcat installed in my server. The communication > happens using AJP 1.3. I'm using the jkmanager URL to activate/deactivate > the tomcat instances. Also, I'm making sure a