A servlet opens an output stream and writes to it for long periods of time. Sometimes it only sends heartbeats to make sure the stream is not closed. The heartbeats should also test whether a stream was closed as to remove it from listening. Unfortunately this does not work everywhere. On a Solaris machine with iPlanet 4.1 for example the servlet does not notice a closed output stream for over an hour! It may never notice it as far as I know because I haven't waited longer than that. The heartbeat is 17 bytes long, sent every minute can come to over 2Kb sent to nowhere. This seemed more than enough on an NT machine running Enterprise 3.6. Meaning the servlet there would get the IOException much quicker. Does anyone know what are the settings that define this behaviour? Has anyone had a problem with the output streams that never seem to get IOExceptions even after browser has quit an hour ago? Any help is greatly appreciated. d. -- David Mossakowski [EMAIL PROTECTED] Programmer 212.310.7275 Instinet Corporation "I don't sit idly by, I'm planning a big surprise" ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
