You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2006/09/14 20:04:21 UTC

DO NOT REPLY [Bug 40498] - connection_pool_timeout is not really respected

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


rainer.jung@kippdata.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




------- Additional Comments From rainer.jung@kippdata.de  2006-09-14 18:04 -------
We will clarify documentation, that the default value "0" disables the timeout,
not the pooling.

Although we could implement "0" as no pooling and "-1" as no timeout, this
dramatically changes the pool behaviour for all existing configurations. As a
consequence we need to keep the meaning of the default value "0" the same.

If you need to really immediately close each connection after use, the upcoming
version 1.2.19 will include the new JkOption DisableReuse for Apache. You should
carefuly consider, if you really need this behaviour. It is very bad for
performance and usually not a good idea.


-- 
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: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org