You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/03/22 03:27:21 UTC
DO NOT REPLY [Bug 17014] -
ServletResponse.flushBuffer() no longer commits the response
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=17014>.
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=17014
ServletResponse.flushBuffer() no longer commits the response
------- Additional Comments From wenjun@creditex.com 2003-03-22 02:27 -------
I am seeing the same problem after upgrading from 4.0.1 to 4.1.18-21.
There are definitely delays for client side to get response. It
happens intermittenly and is not easy to reproduce yet consistently enough
to becomes a performance issue. I am seeing the problem with TC4.1.18+
running in Windows 2000 and Solaris 2.6 with jdk1.3 and jdk1.4. If I
install the legacy http connector, it works fine.
The server code is very simple:
public void doGet(HttpServletRequest req, HttpServletResponse res) throws
javax.servlet.ServletException {
res.setStatus(res.SC_OK);
PrintWriter out = null;
// generate response and assign to tmp
out = res.getWriter();
res.setContentType("text/plain");
out.write(tmp);
out.flush();
out.close();
}
The same code has been working great with TC4.0.1.
Any help is greatly appreciated.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org