[ https://issues.apache.org/jira/browse/CAMEL-8123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14257190#comment-14257190 ]
ASF GitHub Bot commented on CAMEL-8123: --------------------------------------- Github user peterberkman closed the pull request at: https://github.com/apache/camel/pull/349 > Mina2 SSL initiates handshake backwards > --------------------------------------- > > Key: CAMEL-8123 > URL: https://issues.apache.org/jira/browse/CAMEL-8123 > Project: Camel > Issue Type: Bug > Components: camel-mina2 > Affects Versions: 2.13.3, 2.14.0 > Reporter: Justin Cozzens > Assignee: Willem Jiang > Fix For: 2.13.4, 2.14.1, 2.15.0 > > > The Mina2Consumer and Mina2Producer are configured backwards for SSL > handshake initiation. The consumer is trying to initiate the handshake rather > than the producer. You can see this by setting up a SSL enabled consuming > route and telnet to the port, you will immediately get some data sent from > the server to the client rather than the server waiting on the client to > initiate the handshake. > The issue is Mina2Consumer:160, it is setting UseClientMode to true, it > should be false. Mina2Producer line 313 needs to also change to the following: > SslFilter filter = new > SslFilter(configuration.getSslContextParameters().createSSLContext(), > configuration.isAutoStartTls()); > filter.setUseClientMode(true); > connector.getFilterChain().addFirst("sslFilter", filter); > As far as I can tell this has been a bug since this component was introduced. -- This message was sent by Atlassian JIRA (v6.3.4#6332)