- From: Edwin Brown <edbrown@Radix.Net>
- Date: Sun, 21 Feb 1999 20:09:23 -0500 (EST)
- To: www-jigsaw@w3.org
On Mon, 22 Feb 1999, Roland Mainz wrote: > Date: Mon, 22 Feb 1999 00:54:08 +0100 > From: Roland Mainz <Roland.Mainz@informatik.med.uni-giessen.de> > To: W3 Jigsaw Mailinglist <www-jigsaw@w3.org> > Subject: jigsaw problem with servlets and ServletException... > Resent-Date: Sun, 21 Feb 1999 18:53:41 -0500 (EST) > Resent-From: www-jigsaw@w3.org > > > Hi ! > > ---- > > I figured out a problem with jigsaw and servlets: > > If a servlet does not .close() the output stream, jigsaw seems to run > out of open files > after some - ähm - xxxx service cycles. This problem mainly occurs if a > servlet > throws a ServletException (or any other Exception); and some other > servlet examples > simply missing a .close() statement. > > > Solution: jigsaw's ServletOutputStream should check if the stream was > closed or not > (e.g. a method like out.wasClosed()). > A non-closed stream should be closed, but a warning should be written to > stderr and > servlet log (except a ServletException was thrown; I don't know whether > the servlet > specs saying something about this case or not...). This is not Jigsaw's responsibility. This is the coder's responsibility. --- Brilliance In Software Concepts, Inc. Specializing in GUI programing. Java/C/Ada/Unix/VMS finger edbrown@saltmine.radix.net http://www.radix.net/~edbrown
Received on Monday, 22 February 1999 04:33:55 UTC