Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsWhite Papers
Discussion GroupsFirst AidDatabasesJavaBeansGUIJava 3DVirtual MachineCORBASecurityToolsGeneral
Java DirectoryOpen Source ProjectsSample Book ChaptersUser GroupsWeb Resources
Related Topics
Databases.NETMore Topics ...

Java Forum / First Aid / May 2004

Tip: Looking for answers? Try searching our database.

HTTPServletResponse  is not closing the socket connection

Thread view: 
Naresh Agarwal - 29 May 2004 09:51 GMT
Hi

I want HTTPServletResponse to *close* the socket after sending the
response. For this I'm closing the OutputStream after writing the
data. But still socket is not closed and client keeps on waiting to
read data from socket.

And surprisingly this happens only if I use multipart/related in
Content-Type in the response.

Is there way to enfore HTTPServletResponse to close the server socket?

Also, is there any relation between setConentLength header of
HTTPServletResponse and whether the server will "keep-alive" the
socket connection?

thanks,
Naresh
Mike Baranczak - 01 Jun 2004 00:55 GMT
> Hi
>
[quoted text clipped - 7 lines]
>
> Is there way to enfore HTTPServletResponse to close the server socket?

Call flushBuffer() on the HTTPServletResponse. This will send all
buffered data to the client. I think this is what you were looking for.

-MB


Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.