There are four Tomcat 4 bug reports filed on this problem.
There was one bug report filed for Tomcat 5 and Remy applied a
small patch to fix it.
Problems with expiring sessions have been reported numerous times.
The basic problem is as follows, starting at time 0 min and with
a max inactive inter
Howdy,
>Yes, the spec is not in sync with the javadoc. Neither one has been
changed
>since the version 2.2 of the spec. Which one should one trust more?
Ask the JSR expert group for clarifications.
>The reproduction code and the server log is shown below. I used tomcat
Please open a bugzilla i
>Howdy,
>>Reading the servlet spec raised a couple of thoughts about http session
>The servlet spec v2.4, I hope?
The servlet spec v2.4, final release.
>>"SRV.7.6 Last Accessed Times
>>The getLastAccessedTime method of the HttpSession interface allows a
>>servlet
>>to determine the last time th
Howdy,
>Reading the servlet spec raised a couple of thoughts about http session
The servlet spec v2.4, I hope?
>Should I write a patch for these?
Not yet.
>"SRV.7.6 Last Accessed Times
>The getLastAccessedTime method of the HttpSession interface allows a
>servlet
>to determine the last time t
Reading the servlet spec raised a couple of thoughts about http session
handling to my mind. I did verify them, but did not file bug reports.
Should I write a patch for these?
Thought #1
==
"SRV.7.6 Last Accessed Times
The getLastAccessedTime method of the HttpSession interface allows a servlet
