W3C home > Mailing lists > Public > www-jigsaw@w3.org > January to February 1999

Re: Jigsaw hangs during (or maybe after ??) servlet processing...

From: Roland Mainz <Roland.Mainz@informatik.med.uni-giessen.de>
Date: Mon, 22 Feb 1999 11:15:29 +0100
Message-Id: <36D12E40.66E4AF27@informatik.med.uni-giessen.de>
To: Yves Lafon <ylafon@w3.org>, W3 Jigsaw Mailinglist <www-jigsaw@w3.org>

Hi !


Yves Lafon wrote:

> On Mon, 22 Feb 1999, Roland Mainz wrote:
> > My meaning, too (after I found the problem in a third-party servlet).
> > But as I wrote in the other thread about servlet here, jigsaw's
> > subclass implemenation of ServletOutputStream should check this
> > explicitly, close the stream if not closed my the servlet, and fire up
> > a warning in this case...
> It may be a problem (to close the stream). If the servlet is called from a
> SSI for example. But I think that Benoit did a fix to close automatically
> the stream, but it may be not bulletproof and it is better to take care of
> that in the servlet itself :)

Yes, but many examples (like those in the JSDK 2.0 and in a book about
servlets which was used to build most of our Oracle-Servlets) are simply
missing out.close().
A warning would be nice here to gave the servlet programmer a hint that
something will go terribly wrong...

What's the problem with SSI and closing the servlet stream ?
What about adding all ServletOutputStreams in a per-servlet-Vector.
If the servlet is destroyed(), the remaining open servlet streams get
closed, too...

(BTW: Is there a was in JAVA to check how many files can be opened ?)



  __ .  . __
 (o.\ \/ /.o)  Roland Mainz                               C programmer
  \__\/\/__/   Roland.Mainz@informatik.med.uni-giessen.de MPEG specialist
  /O /==\ O\   gisburn@w-specht.rhein-ruhr.de             Sun&&Amiga programmer
 (;O/ \/ \O;)  TEL +49 (0) 2426901568  FAX +49 (0) 2426901569
Received on Monday, 22 February 1999 05:14:45 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:33 UTC