AW: mod-jk loadbalancing: Tomcat is down or refused connection. No response has been sent to the client (yet)

2006-07-26 Thread Michael Huettermann
Hi Rainer, Thanks for the hint. :) Michael -Ursprüngliche Nachricht- Von: Rainer Jung [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 25. Juli 2006 20:39 An: Tomcat Users List Betreff: Re: mod-jk loadbalancing: Tomcat is down or refused connection. No response has been sent to the

mod-jk loadbalancing: Tomcat is down or refused connection. No response has been sent to the client (yet)

2006-07-25 Thread Michael Huettermann
Hello. I try to set up an Apache Web Server loadbalancing incoming requests to a JBoss Cluster (respectively to its Tomcat. For testing purposes the cluster loadbalancing is limited to one node, see below). Everything looks pretty nice, unfortunately Apache Web Server tells me Service

RE: mod-jk loadbalancing: Tomcat is down or refused connection. No response has been sent to the client (yet)

2006-07-25 Thread Raghupathy,Gurumoorthy
Your 8180 is a HTTP connector rather than AJP13 connector ... Make changes in the server.xml of tomcat to enable AJP13 on 8180 ... And then restart both tomcat and apache ... Regards Guru Gurumoorthy Raghupathy Systems Operations - Fidelity Investments International * Tel: +44 1737 836798 *

AW: mod-jk loadbalancing: Tomcat is down or refused connection. No response has been sent to the client (yet)

2006-07-25 Thread Michael Huettermann
Oh thanks, Guru, I did not see the wood for the trees. Thanks a lot. :) Regards Michael -Ursprüngliche Nachricht- Von: Raghupathy,Gurumoorthy [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 25. Juli 2006 14:36 An: 'Tomcat Users List' Betreff: RE: mod-jk loadbalancing: Tomcat is down or

Re: mod-jk loadbalancing: Tomcat is down or refused connection. No response has been sent to the client (yet)

2006-07-25 Thread Rainer Jung
Hi Michael, Michael Huettermann schrieb: The whole system is on my desktop: Apache/2.0.55 (Win32) mod_jk/1.2.17 when using Apache 2 depending on the used MPM the worker cachesize should not be 1: worker.node1.cachesize=1 #worker.node2.cachesize=1 If your MPM is prefork, then 1 is actually