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 5829] - StandardManager needs to cope with sessions throwing exception in read/write
Date Thu, 06 Jun 2002 10:50:00 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=5829>.
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=5829

StandardManager needs to cope with sessions throwing exception in read/write





------- Additional Comments From dsl@ts.com  2002-06-06 10:49 -------
yes indeed it could create hundreds of files, it's also slower than a single
object output stream on account of having to reserialize stuff that is common
across multiple sessions - but it would at least work, it plugs a problem that
can occur unwittingly in a defaultly-configured webapp.  We've been using my
patch here on a high volumne transaction site, and it's worked a treat.  JDBC is
the proper way of doing it, granted, and had things worked when I originally
came to our project I'd have used it.  JDBC needs a little more configuration
than the standard serialization method too.

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


Mime
View raw message