tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Einfeldt" <ralph.einfe...@uptime-isc.de>
Subject AW: non-serializable objects in sessions
Date Tue, 13 Nov 2001 08:12:31 GMT
It is not a good idea at all to store the standard
Connections and ResultSets in the session.

- This will eat up your connections to the database
- The ResultSet is tied to a Connection, this connection
  may timeout at any given time. The database server
  can decide on any criteria it likes to close the 
  underlying connection. (Typically an inactivity timeout)

Possible solution:
- Use a CachedResultSet; some ConnectionPools implement 
  something like that, or have a look at 
  http://developer.java.sun.com/developer/earlyAccess/crs/
  (Requires login)

> -----Urspr√ľngliche Nachricht-----
> Von: Marko Asplund [mailto:aspa@kronodoc.fi]
> Gesendet: Montag, 12. November 2001 19:49
> An: Tomcat Users List
> Betreff: Re: non-serializable objects in sessions
<snip/
> what i'd like to do is store Statement and ResultSet objects in a user
> session so, that the data fetched from the database can be 
> paginated more easily for the user.
<snip/

--
To unsubscribe:   <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
For additional commands: <mailto:tomcat-user-help@jakarta.apache.org>
Troubles with the list: <mailto:tomcat-user-owner@jakarta.apache.org>


Mime
View raw message