tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 15463] - StandardManager incorrectly uses getLastAccessedTime
Date Thu, 01 May 2003 21:50:11 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.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://nagoya.apache.org/bugzilla/show_bug.cgi?id=15463

StandardManager incorrectly uses getLastAccessedTime





------- Additional Comments From tom.clowers@expeditors.com  2003-05-01 21:50 -------
We found this bug also with moving our application from Tomcat 3.3.1 to 
4.1.18/24. I have attached the following files in order that someone may 
attempt to reproduce the error. The whole project is available in attachment 
JSPTester.zip.

JSPTesterServlet.java
MyHTTPSessionListener.java
web.xml

In addition set the session timeout value to one minute in the default web.xml.

    <session-config>
        <session-timeout>1</session-timeout>
    </session-config>

and add an appropriate <Context/> tag to the <Host> section

<Host>
....
  <Context path="/jsptester/servlet" docBase="D:\projects\JSPTester"    
workDir="D:\projects\JSPTester\work\org\apache\jsp" />
....
</Host>

In addition I tried the workaround that Philippe suggests of hitting the server 
twice for each "keepalive". This seems to work.

Tom Clowers
Expeditors International of WA, Inc.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message