[
https://issues.apache.org/jira/browse/PROTON-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16696169#comment-16696169
]
ASF subversion and git services commented on PROTON-1972:
---------------------------------------------------------
Commit a2029ab82f0e10244272869c0e36cf1803e7f548 in qpid-proton-j's branch
refs/heads/master from [~gemmellr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton-j.git;h=a2029ab ]
PROTON-1972: fix test failures when using TLSv1.3 / Java11
> test failures with TLS 1.3 / Java 11
> ------------------------------------
>
> Key: PROTON-1972
> URL: https://issues.apache.org/jira/browse/PROTON-1972
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-j
> Affects Versions: proton-j-0.30.0
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Priority: Major
> Fix For: proton-j-0.31.0
>
>
> Java 11 enables/uses TLS 1.3 by default, and some of the SSL tests fail in
> this scenario. Debugging [eventually] showed that the updated handshake
> behaviour can result in further input accumulating in the input buffer while
> output/wrap is needed to continue the handshake, due to the manner in which
> the SSLEngine is used by the transport but in particular also with how the
> tests use the transport meaning the following input can't get processed (as
> no new input follows it to prompt it) and the handshake doesn't complete.
> Some ad-hoc non-test usage didn't encounter the issue but could theoretically.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
