https://issues.apache.org/bugzilla/show_bug.cgi?id=53717
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from Mark Thomas <ma...@apache.org> ---
I have traced this behaviour to the following:
http://hg.openjdk.java.net/jdk7u/jdk7u6-gate/jdk/diff/14d8cc19f227/src/share/classes/sun/security/ssl/AppOutputStream.java
Switching to TLSv1.1 or later reduces the problem but even switching to TLSv1.2
(available in Java 7) doesn't eliminate the problem entirely. There are still a
handful of small reads.
I haven't dug into this too much but this is definitely a JRE feature. It may
also be a side-effect of something the JRE has to do as part of the SSL/TLS
implementation. Generally, it appears the is.read() on a secure connection will
only ever read a single SSL data record even if multiple records are available
to read. I'd expect records to be read until the internal buffer was full.
Anyway, this is not a Tomcat problem.
--
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
