https://bz.apache.org/bugzilla/show_bug.cgi?id=60750
Mark Thomas changed:
What|Removed |Added
Status|NEW |RESOLVED
https://bz.apache.org/bugzilla/show_bug.cgi?id=60750
--- Comment #27 from Mark Thomas ---
The current 8.0.x code also does not emit the final chunk. This behaviour is
correct.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60750
--- Comment #26 from Mark Thomas ---
This is what I was thinking of from 2014
http://markmail.org/thread/znillhttbmvsl5e5
and the change to close the connection without the final chunk was back-ported
to 8.0.x and 7.0.x.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60750
--- Comment #25 from Mark Thomas ---
I'm leaning towards fixing it but... I do recall we had a discussion around
this topic or one similar in the past. Let me see if I can find a reference to
it.
--
You are receiving this
https://bz.apache.org/bugzilla/show_bug.cgi?id=60750
--- Comment #24 from Christopher Schultz ---
It sounds like this should really be WONTFIX: Tomcat 7.0.x and 8.0.x will emit
a 0-byte final chunk, and changing that in the 7.0.x or 8.0.x branches should
probably
https://bz.apache.org/bugzilla/show_bug.cgi?id=60750
--- Comment #23 from Mark Thomas ---
As does 8.5.x
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscribe, e-mail:
https://bz.apache.org/bugzilla/show_bug.cgi?id=60750
--- Comment #22 from Mark Thomas ---
9.0.x behaves as expected and closes the connection without a final chunk.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60750
Chuck Caldarale changed:
What|Removed |Added
Version|7.0.0 |7.0.70
https://bz.apache.org/bugzilla/show_bug.cgi?id=60750
sharan changed:
What|Removed |Added
Version|7.0.70 |7.0.0
--
You are
https://bz.apache.org/bugzilla/show_bug.cgi?id=60750
--- Comment #21 from Christopher Schultz ---
(In reply to Konstantin Kolinko from comment #20)
> the correct behaviour after an OOM like that is to abort the connection,
> without any terminating chunk.
Okay,
https://bz.apache.org/bugzilla/show_bug.cgi?id=60750
--- Comment #20 from Konstantin Kolinko ---
(In reply to Christopher Schultz from comment #19)
> Tomcat 7.0.76 chokes on this JSP in the way that qixiaobo...@gmail.com has
> described. Here are the TCP responses from
https://bz.apache.org/bugzilla/show_bug.cgi?id=60750
Christopher Schultz changed:
What|Removed |Added
Status|NEEDINFO
https://bz.apache.org/bugzilla/show_bug.cgi?id=60750
--- Comment #18 from Christopher Schultz ---
The following JSP runs (somewhat) correctly on Tomcat 8.0.41. It emits 2
chunks, then intentionally causes an OOME before the third section of the
response. Tomcat
https://bz.apache.org/bugzilla/show_bug.cgi?id=60750
Mark Thomas changed:
What|Removed |Added
Status|NEW |NEEDINFO
--- Comment
https://bz.apache.org/bugzilla/show_bug.cgi?id=60750
qixiaobo...@gmail.com changed:
What|Removed |Added
Status|NEEDINFO|NEW
--
You are receiving this
https://bz.apache.org/bugzilla/show_bug.cgi?id=60750
--- Comment #16 from qixiaobo...@gmail.com ---
(In reply to Ty from comment #14)
> > OOMEs can happen for a number of reasons -- not always complete
> > heap-exhaustion.
>
> Very true, I forgot about the "initialize an object array of
>
Informo que alterei meu email para dea.san...@infobase.com.br
Dea Pacheco
Obrigado
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
https://bz.apache.org/bugzilla/show_bug.cgi?id=60750
--- Comment #15 from qixiaobo...@gmail.com ---
Sorry for my late response.
This request will logout my application. I think there is something wrong with
shiro framework.
in localhost.2017-02-23.log:
https://bz.apache.org/bugzilla/show_bug.cgi?id=60750
--- Comment #14 from Ty ---
> OOMEs can happen for a number of reasons -- not always complete
> heap-exhaustion.
Very true, I forgot about the "initialize an object array of
size=Integer.MAX_VALUE" operations that OOME
https://bz.apache.org/bugzilla/show_bug.cgi?id=60750
--- Comment #13 from Christopher Schultz ---
(In reply to Ty from comment #12)
> - there is no OOME in stdout or stderr
I seem to recall some try/catch code in certain places in Tomcat that swallowed
exceptions
https://bz.apache.org/bugzilla/show_bug.cgi?id=60750
--- Comment #12 from Ty ---
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
https://bz.apache.org/bugzilla/show_bug.cgi?id=60750
Mark Thomas changed:
What|Removed |Added
Status|REOPENED|NEEDINFO
--- Comment
https://bz.apache.org/bugzilla/show_bug.cgi?id=60750
--- Comment #10 from Christopher Schultz ---
(In reply to qixiaobo.nj from comment #5)
> Very simple code!
>
> OutputStream out = outputMessage.getBody();
What type is the "outputMessage" reference? You
https://bz.apache.org/bugzilla/show_bug.cgi?id=60750
--- Comment #9 from Konstantin Kolinko ---
> Server number: 7.0.70.0
You are using Tomcat 7.0.70. The current version of Tomcat 7 is 7.0.75.
I wonder whether the behaviour is reproducible with Tomcat 7.0.75.
https://bz.apache.org/bugzilla/show_bug.cgi?id=60750
Konstantin Kolinko changed:
What|Removed |Added
Summary|still content-length header |A
25 matches
Mail list logo