https://bz.apache.org/bugzilla/show_bug.cgi?id=60750
--- Comment #12 from Ty <ty733...@gmail.com> --- qixiaobo.nj, please try increasing your max heap. We ran into this exact situation last week. The entire response is delivered to the browser, except that one crucial part (the zero-byte chunk signalling the end of the data stream). Like qixiaobo.nj, we were seeing it in some environments but not others. Gradually we merged configs from those environments and found that increasing the heap max (in our case, more than doubling it) resolved the issue. The behavior was unusual in many ways: - again, the entire data stream was delivered to the browser, just not that "0". - the server seems to *think* it sent a complete response (it logged the response summary to the access log) - there is no OOME in stdout or stderr - there is no tell-tale sign of memory trouble, or even an increase in memory utilization in JMX+JConsole - in our case, the data stream size (about 700K) was several orders of magnitude smaller than the max heap (768m). Unfortunately I don't have any better info than qixiaobo.nj as to how this can be reproduced. The application we were dealing with is heavily dependent on third-party libraries and I don't have any evidence where the problem lies. I figured I'd leave this here for qixiaobo.nj or anyone else who runs across this. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
