[ 
https://issues.apache.org/jira/browse/AMQ-8169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17296360#comment-17296360
 ] 

Matt Pavlovich commented on AMQ-8169:
-------------------------------------

[~tetlucas] interesting the stack and the NIOSSLTransport indicate SSLEngine in 
use.. I wonder if we need to fix this (from your JDK changelog notes):

{noformat}
4. TLS connection issues with applications using javax.net.ssl.SSLEngine

Cause: The internal implementation of the SSLEngine and associated classes has 
been reworked with the introduction of TLS v1.3 support. Buffer usage has been 
improved in the SSLEngine area.

Solution: If an SSLEngine application encounters issues after upgrading to JDK 
8u261 or later, refer to the Java 8 API to ensure application code is correct. 
In particular, applications using SSLEngine should not just depend on 
SSLEngineResult.Status.BUFFER_UNDERFLOW or 
SSLEngineResult.Status.BUFFER_OVERFLOW results in order to flush pending data. 
Buffers should always be flushed after an SSLEngine wrap operation if such a 
call produces data (where SSLEngineResult.Status.OK may be returned).
{noformat}

> StompNIOSSLTest test fails with more recent JDK 8 versions
> ----------------------------------------------------------
>
>                 Key: AMQ-8169
>                 URL: https://issues.apache.org/jira/browse/AMQ-8169
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.17.0
>            Reporter: Matt Pavlovich
>            Assignee: Jean-Baptiste Onofré
>            Priority: Major
>             Fix For: 5.17.0
>
>
> The StompNIOSSL test fails during CI/CD tests with certain JDK versions. This 
> blocks PR's from getting a green status
> To reproduce:
> [x] Fails with jdk1.8.0_281
> [x] Passes with jdk1.8.0_211
> Suspects:
> * The test SSL cert needs to be generated with a newer cipher and/or length 
> * The NIOSSLTransport has a bad byte[] read bug



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to