Re: increase the backend idle connection timeout or the connection_pool_minsize
Hi, I think in mod_jk 1.2.20 these old parameters changed with new parameter names, these old paramter does not take effect into your mod_jk. Please change them with new name. Please refer URL for more details changes in new mod_jk: http://tomcat.apache.org/connectors-doc/reference/printer/workers.html worker.tomcat-publicweb-01.cachesize=10 worker.tomcat-publicweb-01.cache_timeout=600 It should be: worker.tomcat-publicweb-01.connection_pool_size=10 worker.tomcat-publicweb-01.connection_pool_timeout=600 worker.tomcat-publicweb-01.connection_pool_minsize=6 I also suggest to increase the nos for worker.tomcat-publicweb-01.connection_pool_size=50 worker.tomcat-publicweb-01.connection_pool_minsize=26 This modification you need to do in workers.properties. Please update this does not help. With regards, Babu Satasiya Cisco System Inc. Fletcher Cocquyt wrote: Rainer Jung rainer.jung at kippdata.de writes: Yes, but the log message is talking about the min size. The default min size is size/2, but we changed it between 1.2.19 and 1.2.20 to (size+1)/2. So for prefork the min size was 0 until 1.2.19 and is 1 starting with 1.2.20. So I tried connection_pool_minsize=1 - no discernable effect on error rate I've tried tuning all the other suggested parameters without a noticable effect on the rate of these info messages (2000-3000/hour) I tried: maxActive 40, maxIdle 5, maxWait 3000 no discernable difference in error rate. Maybe I need to modify them with bigger deltas to see a difference? Is there a way to tell which parameter would have the most impact? If those are for a DataSource, they have no relation to your mod_jk messages. Yes, maxActive 40, maxIdle 5, maxWait 3000 are all in the context.xml file in the datasource definition - so these would not affect mod_jk messages - I get that now! I tried connectionTimeout = 60 (10 times the default of 60 seconds) - no reduction in error rate Are you sure, you put it into the correct connector? I put it into the server.xml AJP connector - actually I'm not sure now if I had the value in quotes: Server port=13135 shutdown=SHUTDOWN Service name=Catalina Connector port=13138 / Connector port=13139 protocol=AJP/1.3 connectionTimeout=60 / Engine name=Catalina defaultHost=localhost jvmRoute=tomcat-publicweb-01 Logger className=org.apache.catalina.logger.FileLogger / Host name=localhost appBase=webapps / /Engine /Service /Server Please post your version numbers, platform details, log example and relevant apache and tomcat configuration items. Web servers: Solaris 9 x86, Apache 2.0.52, mod_jk 1.2.20 App servers: Solaris 9 Sparc, tomcat 5.0 worker definition: worker.tomcat-publicweb-01.type=ajp13 worker.tomcat-publicweb-01.host=irt-app-01 worker.tomcat-publicweb-01.port=13139 worker.tomcat-publicweb-01.lbfactor=50 worker.tomcat-publicweb-01.cachesize=10 worker.tomcat-publicweb-01.cache_timeout=600 worker.tomcat-publicweb-01.socket_keepalive=1 worker.tomcat-publicweb-01.retries=2 worker.tomcat-publicweb-01.socket_timeout=30 worker.tomcat-publicweb-01.connect_timeout=2000 worker.tomcat-publicweb-01.prepost_timeout=5000 worker.tomcat-publicweb-01.reply_timeout=30 mod_jk errors: ajp_send_request::jk_ajp_common.c (1201): (tomcat-publicweb-01) error sending request. Will try another pooled connection ajp_send_request::jk_ajp_common.c (1227): (tomcat-publicweb-01) all endpoints are disconnected ajp_send_request::jk_ajp_common.c (1230): (tomcat-publicweb-01) increase the backend idle connection timeout or the connection_pool_minsize ajp_service::jk_ajp_common.c (1916): (tomcat-publicweb-01) sending request to tomcat failed, recoverable operation attempt=1 - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/increase-the-backend-idle-connection-timeout-or-the-connection_pool_minsize-tf3294954.html#a9718414 Sent from the Tomcat - User mailing list archive at Nabble.com. - 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: increase the backend idle connection timeout or the connection_pool_minsize
on that connection pool size, these two: parameter namemaxActive/name value20/value /parameter parameter namemaxIdle/name value2/value /parameter You're also only allowing 1 sec to connect it appears. Might ratchet it up a little more. -Original Message- From: news [mailto:[EMAIL PROTECTED] Behalf Of Fletcher Cocquyt Sent: Monday, February 26, 2007 12:32 PM To: users@tomcat.apache.org Subject: increase the backend idle connection timeout or the connection_pool_minsize Hi, This is a followup to my Feb14 post: Re: socket is not connected any more (errno=11) I've just upgraded from 1.2.19 to 1.2.20 and the new log messages are: increase the backend idle connection timeout or the connection_pool_minsize I could not find much on which parameters this is referring to? On the mod_jk side I have: worker.tomcat-publicweb-01.type=ajp13 worker.tomcat-publicweb-01.host=app-01 worker.tomcat-publicweb-01.port=12345 worker.tomcat-publicweb-01.lbfactor=50 worker.tomcat-publicweb-01.cachesize=10 worker.tomcat-publicweb-01.cache_timeout=600 worker.tomcat-publicweb-01.socket_keepalive=1 worker.tomcat-publicweb-01.retries=2 worker.tomcat-publicweb-01.socket_timeout=30 worker.tomcat-publicweb-01.connect_timeout=2000 worker.tomcat-publicweb-01.prepost_timeout=5000 worker.tomcat-publicweb-01.reply_timeout=30 On the tomcat side I have: parameter namemaxActive/name value20/value /parameter parameter namemaxIdle/name value2/value /parameter parameter namemaxWait/name value1000/value /parameter parameter namelogAbandoned/name valuetrue/value /parameter parameter nameremoveAbandoned/name valuetrue/value /parameter parameter nameremoveAbandonedTimeout/name value1200/value /parameter Which parameters are these log messages referring to? Many thanks, Fletcher. - 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: increase the backend idle connection timeout or the connection_pool_minsize
Fletcher Cocquyt wrote: Hi, This is a followup to my Feb14 post: Re: socket is not connected any more (errno=11) I've just upgraded from 1.2.19 to 1.2.20 and the new log messages are: increase the backend idle connection timeout or the connection_pool_minsize I could not find much on which parameters this is referring to? On the mod_jk side I have: worker.tomcat-publicweb-01.type=ajp13 worker.tomcat-publicweb-01.host=app-01 worker.tomcat-publicweb-01.port=12345 worker.tomcat-publicweb-01.lbfactor=50 worker.tomcat-publicweb-01.cachesize=10 worker.tomcat-publicweb-01.cache_timeout=600 worker.tomcat-publicweb-01.socket_keepalive=1 worker.tomcat-publicweb-01.retries=2 worker.tomcat-publicweb-01.socket_timeout=30 worker.tomcat-publicweb-01.connect_timeout=2000 worker.tomcat-publicweb-01.prepost_timeout=5000 worker.tomcat-publicweb-01.reply_timeout=30 You can add connection_pool_minsize. See the workers.properties pages in the reference guide. On the tomcat side I have: parameter namemaxActive/name value20/value /parameter parameter namemaxIdle/name value2/value /parameter parameter namemaxWait/name value1000/value /parameter parameter namelogAbandoned/name valuetrue/value /parameter parameter nameremoveAbandoned/name valuetrue/value /parameter parameter nameremoveAbandonedTimeout/name value1200/value /parameter This looks like a DataSource definition (Tomcat to database). The idle connection timeout in the case of tomcat is the value of conncetiontimeout in the Connector element of server.xml. You need to find the AJP/1.3 connector. Which parameters are these log messages referring to? Regards, 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]
Re: increase the backend idle connection timeout or the connection_pool_minsize
Rainer Jung rainer.jung at kippdata.de writes: You can add connection_pool_minsize. See the workers.properties pages in the reference guide. I'm using apache 2.0 prefork - the docs: http://tomcat.apache.org/connectors-doc/reference/workers.html say Do not use connection_pool_size with values higher then 1 on Apache 2.x prefork I've tried tuning all the other suggested parameters without a noticable effect on the rate of these info messages (2000-3000/hour) I tried: maxActive 40, maxIdle 5, maxWait 3000 no discernable difference in error rate. Maybe I need to modify them with bigger deltas to see a difference? Is there a way to tell which parameter would have the most impact? This looks like a DataSource definition (Tomcat to database). The idle connection timeout in the case of tomcat is the value of conncetiontimeout in the Connector element of server.xml. You need to find the AJP/1.3 connector. I tried connectionTimeout = 60 (10 times the default of 60 seconds) - no reduction in error rate thanks - 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: increase the backend idle connection timeout or the connection_pool_minsize
Fletcher Cocquyt schrieb: Rainer Jung rainer.jung at kippdata.de writes: You can add connection_pool_minsize. See the workers.properties pages in the reference guide. I'm using apache 2.0 prefork - the docs: http://tomcat.apache.org/connectors-doc/reference/workers.html say Do not use connection_pool_size with values higher then 1 on Apache 2.x prefork Yes, but the log message is talking about the min size. The default min size is size/2, but we changed it between 1.2.19 and 1.2.20 to (size+1)/2. So for prefork the min size was 0 until 1.2.19 and is 1 starting with 1.2.20. I've tried tuning all the other suggested parameters without a noticable effect on the rate of these info messages (2000-3000/hour) I tried: maxActive 40, maxIdle 5, maxWait 3000 no discernable difference in error rate. Maybe I need to modify them with bigger deltas to see a difference? Is there a way to tell which parameter would have the most impact? If those are for a DataSource, they have no relation to your mod_jk messages. This looks like a DataSource definition (Tomcat to database). The idle connection timeout in the case of tomcat is the value of conncetiontimeout in the Connector element of server.xml. You need to find the AJP/1.3 connector. I tried connectionTimeout = 60 (10 times the default of 60 seconds) - no reduction in error rate Are you sure, you put it into the correct connector? Please post your version numbers, platform details, log example and relevant apache and tomcat configuration items. Regards, 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]
Re: increase the backend idle connection timeout or the connection_pool_minsize
Rainer Jung rainer.jung at kippdata.de writes: Yes, but the log message is talking about the min size. The default min size is size/2, but we changed it between 1.2.19 and 1.2.20 to (size+1)/2. So for prefork the min size was 0 until 1.2.19 and is 1 starting with 1.2.20. So I tried connection_pool_minsize=1 - no discernable effect on error rate I've tried tuning all the other suggested parameters without a noticable effect on the rate of these info messages (2000-3000/hour) I tried: maxActive 40, maxIdle 5, maxWait 3000 no discernable difference in error rate. Maybe I need to modify them with bigger deltas to see a difference? Is there a way to tell which parameter would have the most impact? If those are for a DataSource, they have no relation to your mod_jk messages. Yes, maxActive 40, maxIdle 5, maxWait 3000 are all in the context.xml file in the datasource definition - so these would not affect mod_jk messages - I get that now! I tried connectionTimeout = 60 (10 times the default of 60 seconds) - no reduction in error rate Are you sure, you put it into the correct connector? I put it into the server.xml AJP connector - actually I'm not sure now if I had the value in quotes: Server port=13135 shutdown=SHUTDOWN Service name=Catalina Connector port=13138 / Connector port=13139 protocol=AJP/1.3 connectionTimeout=60 / Engine name=Catalina defaultHost=localhost jvmRoute=tomcat-publicweb-01 Logger className=org.apache.catalina.logger.FileLogger / Host name=localhost appBase=webapps / /Engine /Service /Server Please post your version numbers, platform details, log example and relevant apache and tomcat configuration items. Web servers: Solaris 9 x86, Apache 2.0.52, mod_jk 1.2.20 App servers: Solaris 9 Sparc, tomcat 5.0 worker definition: worker.tomcat-publicweb-01.type=ajp13 worker.tomcat-publicweb-01.host=irt-app-01 worker.tomcat-publicweb-01.port=13139 worker.tomcat-publicweb-01.lbfactor=50 worker.tomcat-publicweb-01.cachesize=10 worker.tomcat-publicweb-01.cache_timeout=600 worker.tomcat-publicweb-01.socket_keepalive=1 worker.tomcat-publicweb-01.retries=2 worker.tomcat-publicweb-01.socket_timeout=30 worker.tomcat-publicweb-01.connect_timeout=2000 worker.tomcat-publicweb-01.prepost_timeout=5000 worker.tomcat-publicweb-01.reply_timeout=30 mod_jk errors: ajp_send_request::jk_ajp_common.c (1201): (tomcat-publicweb-01) error sending request. Will try another pooled connection ajp_send_request::jk_ajp_common.c (1227): (tomcat-publicweb-01) all endpoints are disconnected ajp_send_request::jk_ajp_common.c (1230): (tomcat-publicweb-01) increase the backend idle connection timeout or the connection_pool_minsize ajp_service::jk_ajp_common.c (1916): (tomcat-publicweb-01) sending request to tomcat failed, recoverable operation attempt=1 - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
