DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6160>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6160 HttpServletResponse.flushBuffer() fails to flush data to client ------- Additional Comments From [EMAIL PROTECTED] 2002-02-01 15:40 ------- I tried using the HTTP/1.0 connector defined in the default server.xml which had no affect. I also turned chunking off in the HTTP/1.1 connector with allowChunking="false" which had no affect. Our client is an applet which uses URLConnect to communicate to servlets. For testing I had been running my applets, in appletviewer found in Sun jdk 1.3. The flush failed as previously described. Same results were observed running the applet in Netscape using 1.3.1_01 plugin. I tried using appletviewer in Sun jdk 1.4 and communications started working as expected. All serialized objects were returned individually to client when servlet's output stream was flushed. Also, tomcat 4.0 must be running in jvm 1.4 for flushing to work as expected. Flushing failed when running tomcat 4.0 in 1.3 jvm when using any jvm for client. Obviously there is a work around. However, it creates a linkage between jvm versions used in the server and client, which is a maintenance nightmare for a distributed system. Do you have any ideas where else to look to find root of problem. I would prefer to figure this out and fix rather than rely on work around. thanks -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
