AW: mod-jk loadbalancing: "Tomcat is down or refused connection. No response has been sent to the client (yet)"
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 client (yet)" 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 OK, but if it is "worker" you set it to the number of threads per process. In fact mod_jk when used with Apache determines this value automatically during startup :) You should only use it in case of worker MPM and if you really know a good reason to make the cache smaller than the number of threads. Rainer - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mod-jk loadbalancing: "Tomcat is down or refused connection. No response has been sent to the client (yet)"
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 OK, but if it is "worker" you set it to the number of threads per process. In fact mod_jk when used with Apache determines this value automatically during startup :) You should only use it in case of worker MPM and if you really know a good reason to make the cache smaller than the number of threads. Rainer - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: mod-jk loadbalancing: "Tomcat is down or refused connection. No response has been sent to the client (yet)"
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 refused connection. No response has been sent to the client (yet)" 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 * Internal: 8-724 6798 * Tel (R): +442086610646 * Tel (R): +447899033459 * Tel (S): +447736059647 * Mail-Zone : XTW2A * E-Mail: <<mailto:[EMAIL PROTECTED]>> Important: Fidelity Investments International, Fidelity Investment Services Limited, Fidelity Pensions Management and Financial Administration Services Limited (a Fidelity Group company) are all authorised and regulated in the UK by the Financial Services Authority and have their registered offices at Oakhill House, 130 Tonbridge Road, Hildenborough, Tonbridge, Kent TN11 9DZ. Tel 01732 361144. Fidelity only gives information on products and does not give investment advice to private clients based on individual circumstances. Any comments or statements made are not necessarily those of Fidelity. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you received this in error, please contact the sender and delete the material from any computer. All e-mails sent from or to Fidelity may be subject to our monitoring procedures. 'Direct link to Fidelitys website. <http://www.fidelity-international.com/world/index.html> 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 Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later." The mod_jk.log says (full log below): [Tue Jul 25 13:46:15 2006][4240:4804] [info] jk_ajp_common.c (955): Tomcat has forced a connection close for socket 844 [Tue Jul 25 13:46:15 2006][4240:4804] [error] jk_ajp_common.c (1531): Tomcat is down or refused connection. No response has been sent to the client (yet) [Tue Jul 25 13:46:15 2006][4240:4804] [info] jk_ajp_common.c (1751): Receiving from tomcat failed, recoverable operation attempt=0 [Tue Jul 25 13:46:15 2006][4240:4804] [info] jk_ajp_common.c (1783): Sending request to tomcat failed, recoverable operation attempt= The Tomcat of my JBoss 4.0.2 does not receive any data/request (I see that in its log). The JBoss instance respectively the JBoss' Tomcat directly accepts requests via http://127.0.0.1:8180/test/Servlet successfully. The whole system is on my desktop: Apache/2.0.55 (Win32) mod_jk/1.2.17 The Apache httpd listens on 127.0.0.1 Port Windows XP Professional 2002 SP2, no Firewall on local desktop Thanks for your help. Michael ---Workers.properties (limited to one node to make it more simple)--- # Define list of workers that will be used # for mapping requests worker.list=loadbalancer,status # Define Node1 # modify the host as your host IP or DNS name. worker.node1.port=8180 worker.node1.host=127.0.0.1 worker.node1.type=ajp13 worker.node1.lbfactor=1 worker.node1.cachesize=1 # Define Node2 # currently NOT in use #worker.node2.port=8280 #worker.node2.host=127.0.0.1 #worker.node2.type=ajp13 #worker.node2.lbfactor=1 #worker.node2.cachesize=1 # Load-balancing behaviour worker.loadbalancer.type=lb #worker.loadbalancer.balance_workers=node1,node2 NOT in use worker.loadbalancer.balance_workers=node1 worker.loadbalancer.sticky_session=1 # Status worker for managing load balancer worker.status.type=status -mod-jk.conf- # Load mod_jk module # Specify the filenamC:\Programme\Apache2.2\conf\mod_jk.lib LoadModule jk_module modules\mod_jk.so # Where to find workers.properties JkWorkersFile conf/workers.properties # Where to put jk logs JkLogFile logs/mod_jk.log # Set the jk log level [debug/error/info] JkLogLevel debug # Select the log format JkLogStampFormat "[%a %b %d %H:%M:%S %Y]" # JkOptions indicates to send SSK KEY SIZE JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories # JkRequestLogFormat JkRequestLogFormat "%w %V %T" # Mount your applications JkMount /* loadbalancer # You can use external file for mount points. # It will be checked for updates each 60 second
RE: mod-jk loadbalancing: "Tomcat is down or refused connection. No response has been sent to the client (yet)"
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 * Internal: 8-724 6798 * Tel (R): +442086610646 * Tel (R): +447899033459 * Tel (S): +447736059647 * Mail-Zone : XTW2A * E-Mail: <<mailto:[EMAIL PROTECTED]>> Important: Fidelity Investments International, Fidelity Investment Services Limited, Fidelity Pensions Management and Financial Administration Services Limited (a Fidelity Group company) are all authorised and regulated in the UK by the Financial Services Authority and have their registered offices at Oakhill House, 130 Tonbridge Road, Hildenborough, Tonbridge, Kent TN11 9DZ. Tel 01732 361144. Fidelity only gives information on products and does not give investment advice to private clients based on individual circumstances. Any comments or statements made are not necessarily those of Fidelity. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you received this in error, please contact the sender and delete the material from any computer. All e-mails sent from or to Fidelity may be subject to our monitoring procedures. 'Direct link to Fidelitys website. <http://www.fidelity-international.com/world/index.html> -Original Message- From: Michael Huettermann [mailto:[EMAIL PROTECTED] Sent: 25 July 2006 13:25 To: users@tomcat.apache.org Subject: mod-jk loadbalancing: "Tomcat is down or refused connection. No response has been sent to the client (yet)" 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 Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later." The mod_jk.log says (full log below): [Tue Jul 25 13:46:15 2006][4240:4804] [info] jk_ajp_common.c (955): Tomcat has forced a connection close for socket 844 [Tue Jul 25 13:46:15 2006][4240:4804] [error] jk_ajp_common.c (1531): Tomcat is down or refused connection. No response has been sent to the client (yet) [Tue Jul 25 13:46:15 2006][4240:4804] [info] jk_ajp_common.c (1751): Receiving from tomcat failed, recoverable operation attempt=0 [Tue Jul 25 13:46:15 2006][4240:4804] [info] jk_ajp_common.c (1783): Sending request to tomcat failed, recoverable operation attempt= The Tomcat of my JBoss 4.0.2 does not receive any data/request (I see that in its log). The JBoss instance respectively the JBoss' Tomcat directly accepts requests via http://127.0.0.1:8180/test/Servlet successfully. The whole system is on my desktop: Apache/2.0.55 (Win32) mod_jk/1.2.17 The Apache httpd listens on 127.0.0.1 Port Windows XP Professional 2002 SP2, no Firewall on local desktop Thanks for your help. Michael ---Workers.properties (limited to one node to make it more simple)--- # Define list of workers that will be used # for mapping requests worker.list=loadbalancer,status # Define Node1 # modify the host as your host IP or DNS name. worker.node1.port=8180 worker.node1.host=127.0.0.1 worker.node1.type=ajp13 worker.node1.lbfactor=1 worker.node1.cachesize=1 # Define Node2 # currently NOT in use #worker.node2.port=8280 #worker.node2.host=127.0.0.1 #worker.node2.type=ajp13 #worker.node2.lbfactor=1 #worker.node2.cachesize=1 # Load-balancing behaviour worker.loadbalancer.type=lb #worker.loadbalancer.balance_workers=node1,node2 NOT in use worker.loadbalancer.balance_workers=node1 worker.loadbalancer.sticky_session=1 # Status worker for managing load balancer worker.status.type=status -mod-jk.conf- # Load mod_jk module # Specify the filenamC:\Programme\Apache2.2\conf\mod_jk.lib LoadModule jk_module modules\mod_jk.so # Where to find workers.properties JkWorkersFile conf/workers.properties # Where to put jk logs JkLogFile logs/mod_jk.log # Set the jk log level [debug/error/info] JkLogLevel debug # Select the log format JkLogStampFormat "[%a %b %d %H:%M:%S %Y]" # JkOptions indicates to send SSK KEY SIZE JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories # JkRequestLogFormat JkRequestLogFormat "%w %V %T" # Mount your applications JkMount /* loadbalancer # You can use external file for mount points. # It will be checked for updates each 60 seconds. # The format of the file is: /url=worker # /examples/*=loadbalancer #JkMountFile conf/uriworkermap.properties # Add shared memory. # This dire
mod-jk loadbalancing: "Tomcat is down or refused connection. No response has been sent to the client (yet)"
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 Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later." The mod_jk.log says (full log below): [Tue Jul 25 13:46:15 2006][4240:4804] [info] jk_ajp_common.c (955): Tomcat has forced a connection close for socket 844 [Tue Jul 25 13:46:15 2006][4240:4804] [error] jk_ajp_common.c (1531): Tomcat is down or refused connection. No response has been sent to the client (yet) [Tue Jul 25 13:46:15 2006][4240:4804] [info] jk_ajp_common.c (1751): Receiving from tomcat failed, recoverable operation attempt=0 [Tue Jul 25 13:46:15 2006][4240:4804] [info] jk_ajp_common.c (1783): Sending request to tomcat failed, recoverable operation attempt= The Tomcat of my JBoss 4.0.2 does not receive any data/request (I see that in its log). The JBoss instance respectively the JBoss' Tomcat directly accepts requests via http://127.0.0.1:8180/test/Servlet successfully. The whole system is on my desktop: Apache/2.0.55 (Win32) mod_jk/1.2.17 The Apache httpd listens on 127.0.0.1 Port Windows XP Professional 2002 SP2, no Firewall on local desktop Thanks for your help. Michael ---Workers.properties (limited to one node to make it more simple)--- # Define list of workers that will be used # for mapping requests worker.list=loadbalancer,status # Define Node1 # modify the host as your host IP or DNS name. worker.node1.port=8180 worker.node1.host=127.0.0.1 worker.node1.type=ajp13 worker.node1.lbfactor=1 worker.node1.cachesize=1 # Define Node2 # currently NOT in use #worker.node2.port=8280 #worker.node2.host=127.0.0.1 #worker.node2.type=ajp13 #worker.node2.lbfactor=1 #worker.node2.cachesize=1 # Load-balancing behaviour worker.loadbalancer.type=lb #worker.loadbalancer.balance_workers=node1,node2 NOT in use worker.loadbalancer.balance_workers=node1 worker.loadbalancer.sticky_session=1 # Status worker for managing load balancer worker.status.type=status -mod-jk.conf- # Load mod_jk module # Specify the filenamC:\Programme\Apache2.2\conf\mod_jk.lib LoadModule jk_module modules\mod_jk.so # Where to find workers.properties JkWorkersFile conf/workers.properties # Where to put jk logs JkLogFile logs/mod_jk.log # Set the jk log level [debug/error/info] JkLogLevel debug # Select the log format JkLogStampFormat "[%a %b %d %H:%M:%S %Y]" # JkOptions indicates to send SSK KEY SIZE JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories # JkRequestLogFormat JkRequestLogFormat "%w %V %T" # Mount your applications JkMount /* loadbalancer # You can use external file for mount points. # It will be checked for updates each 60 seconds. # The format of the file is: /url=worker # /examples/*=loadbalancer #JkMountFile conf/uriworkermap.properties # Add shared memory. # This directive is present with 1.2.10 and # later versions of mod_jk, and is needed for # for load balancing to work properly JkShmFile logs/jk.shm # Add jkstatus for managing runtime data JkMount status Order deny,allow Deny from all Allow from 127.0.0.1 --Full mod_jk.log- [Tue Jul 25 13:45:46 2006][5488:5540] [debug] jk_shm.c (135): Initialized shared memory size=24704 free=24576 addr=0x94 [Tue Jul 25 13:45:46 2006][5488:5540] [debug] mod_jk.c (2355): Initialized shm:memory [Tue Jul 25 13:45:46 2006][5488:5540] [debug] jk_uri_worker_map.c (361): rule map size is 2 [Tue Jul 25 13:45:46 2006][5488:5540] [debug] jk_uri_worker_map.c (298): wildchar rule /*=loadbalancer was added [Tue Jul 25 13:45:46 2006][5488:5540] [debug] jk_uri_worker_map.c (306): exact rule /jkstatus/=status was added [Tue Jul 25 13:45:46 2006][5488:5540] [debug] jk_worker.c (236): creating worker loadbalancer [Tue Jul 25 13:45:46 2006][5488:5540] [debug] jk_worker.c (141): about to create instance loadbalancer of lb [Tue Jul 25 13:45:46 2006][5488:5540] [debug] jk_worker.c (154): about to validate and init loadbalancer [Tue Jul 25 13:45:46 2006][5488:5540] [debug] jk_worker.c (141): about to create instance node1 of ajp13 [Tue Jul 25 13:45:46 2006][5488:5540] [debug] jk_worker.c (154): about to validate and init node1 [Tue Jul 25 13:45:46 2006][5488:5540] [debug] jk_ajp_common.c (1842): worker node1 contact is '127.0.0.1:8180' [Tue Jul 25 13:45:46 2006][5488:5540] [debug] jk_ajp_common.c (1965): setting endpoint options: [Tue Jul 25 13:45:46 2006][5488:5540] [debug] jk_ajp_common.c (1968): keepalive:0 [Tue Jul 25 13:45:46 2006][5488:5540] [debug] jk_ajp_common.c (1972): timeout: -1 [Tue Jul 25 13:45:46 2006][5488:5540] [de
