DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=40498>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=40498 Summary: connection_pool_timeout is not really respected Product: Tomcat 5 Version: Unknown Platform: Sun OS/Version: Solaris Status: NEW Severity: normal Priority: P3 Component: Connector:AJP AssignedTo: tomcat-dev@jakarta.apache.org ReportedBy: [EMAIL PROTECTED] connection_pool_timeout (or former recycle_timeout) is set to zero as default to keep the number of AJP 13 connections low. However, many connections stay open, as the evaluation for closing seems to take place when the *next* requests arrives. One should assume that "zero" means "close right after the request". For me, the following patch works fine, but I am not sure enough to suggest it for submission: diff -cr tomcat-connectors-1.2.18-src/native/common/jk_ajp_common.c tomcat-conne ctors-1.2.18-src.new/native/common/jk_ajp_common.c *** tomcat-connectors-1.2.18-src/native/common/jk_ajp_common.c Tue Jul 18 09:19 :27 2006 --- tomcat-connectors-1.2.18-src.new/native/common/jk_ajp_common.c Wed Sep 13 15:42:09 2006 *************** *** 2081,2086 **** --- 2081,2089 ---- ajp_worker_t *w = p->worker; JK_ENTER_CS(&w->cs, rc); + if (p->worker != NULL && p->worker->cache_timeout == 0) + p->reuse = JK_FALSE; + if (rc) { int i, sock = JK_INVALID_SOCKET; -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
