Re: Implementation of a buffer. Sessions and threads timeouts

[Peters, Jim]

Title: Implementation of a buffer. Sessions and threads timeouts

I don't think the session is the proper place for caching result sets.  You would have a cache for each user.  It's better to cache the data in a singleton object, whose handle is held by the servlet(s).  That way mutliple servlets can use the same singleton object.  Re. timed out threads, these can be configured in JRun config files.

-----Original Message-----
From: Marian Haus [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 20, 2001 6:46 AM
To: [EMAIL PROTECTED]
Subject: Implementation of a buffer. Sessions and threads timeouts

Hi!
        I am using a servlet who retrievs information from a database.
During a browser session I want to get the data from the database and then
save the data into a buffer.
        I'm implementing the buffer using the session object of the servlet and I'm saving the data into the buffer
using   "session.setAttribute".
        I can set the timout of the servlet using  "setMaxInactiveInterval(<number of second>)".
        I've noticed that the servlet thread has a "Idle Thread Timeout" with the default value 300 seconds (I am using JRun).

        How can I "synchronise" this "Idle Thread Timeout" with "setMaxInactiveInterval(<number of second>)"?
        Actually the question is how can I find out (or manage) if the thread of my servlet is destroyed or not?

Thanks!

Marian

___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html