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/10/03 23:49:43 UTC

DO NOT REPLY [Bug 15463] - StandardManager incorrectly uses getLastAccessedTime

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=15463>.
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=15463





------- Additional Comments From nick@silvermoongroup.com  2006-10-03 14:49 -------
We are still running Tomcat 4.1.29 and experiencing the timeout problem almost
exactly as as Glenn describes it in comment #9. Is the patch as described there
only available from release 4.1.31 or can we somehow apply it to 4.1.29? If the
latter is true then where do I get this patch, since I can only find the fix
(id=10095) as per comment #4 from Tomcat 3.x days. It seems however from Glenn's
note re the patch and the 4.1.31 release notes that the upgrade path is a better
choice than any quick fix, so  it make sense to upgrade to 4.1.31 if one is
serious to resolve timeout issues, right?

-- 
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