"Santosh Gangadhar" <sant...@wirkle.com> wrote in message news:6a0454270903060913x1e8a7914qbf9de52744236...@mail.gmail.com... > On Fri, Mar 6, 2009 at 8:50 PM, Caldarale, Charles R < > chuck.caldar...@unisys.com> wrote: > >> > From: Santosh Gangadhar [mailto:sant...@wirkle.com] >> > Subject: Re: Problem using chunked encoding - request thread cleanup >> > >> > But the client keeps running because Tomcat as such does >> > not close the stream. >> >> Perhaps I'm missing something, but why would Tomcat ever close the >> chunked-encoding input stream? Isn't it the responsibility of the client >> to >> indicate there's no more data and close the stream? >> >> - Chuck >> >> >> THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY >> MATERIAL and is thus for use only by the intended recipient. If you >> received >> this in error, please contact the sender and delete the e-mail and its >> attachments from all computers. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> The client is pushing an mjpeg stream to a servlet on the server. Its >> upto > the server when to stop pushing the stream. The client cannot indicate > when > to end the stream. May be HTTP is not being used aptly here. But still, is > there a way for the servlet to end the stream. ServletInputStream.close() > does not help either. > Thanks, > Santosh. > No currently released version of Tomcat does what you want. But the upcoming 6.0.19 release will if the Servlet sends back a status code that will cause it to close the connection to the client (e.g. HttpServletResponse.SC_REQUEST_ENTITY_TOO_LARGE), or throws an Exception that isn't handled by an error page.
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
