At 07:08 AM 11/25/2003, you wrote:
Ben,
Thanks for the reply. But I'm still unclear on why setting the
timeout won't work for my situation. What is the difference between an
effectively idle session timing out, and "cancelling" a request?
Of course I agree that fixing the root problem would
A session timeout just means that the next time you hit the site with the same
browser, you will be assigned a new JSPSessionID to bind that transaction
with your session object. It would do nothing to stop a request that's hung.
Think of a "request" as one hit to a server and a "session" as se
Ben,
Thanks for the reply. But I'm still unclear on why setting the timeout won't work
for my situation. What is the difference between an effectively idle session timing
out, and "cancelling" a request?
Of course I agree that fixing the root problem would be preferable, but it's extremely
JSP/Servlet technology uses a solution called the HttpSession to overcome the
limitations of the stateless HTTP protocol.
Tomcat uses cookies to map a particular web user to his/her session object.
The developer can bind objects to a user's session object and then retrieve
them on subsequent hit
Hi,
I'm a relatively new Tomcat user, running 4.0.4 (testing on Windows, deploying on
Sun UNIX). The UNIX servlet is having rare problems "hanging", for which the exact
cause is unknown.
I'm trying to see if a session timeout can solve the problem, but have not been able
to get it to work.
