[jira] [Closed] (AMQ-3128) networkConnection fails when SSLv2 disabled

["Timothy Bish (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQ-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish closed AMQ-3128.
-----------------------------

    Resolution: Cannot Reproduce

I couldn't reproduce this, if you have a unit test that shows the problem please reopen and attach it here. 
                
> networkConnection fails when SSLv2 disabled
> -------------------------------------------
>
>                 Key: AMQ-3128
>                 URL: https://issues.apache.org/jira/browse/AMQ-3128
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.4.2
>            Reporter: Adam Sussman
>
> Given a broker transportConnection with SSLv2 disabled, networkConnectors fail to connect with error:
> ERROR:  Could not accept connection : javax.net.ssl.SSLHandshakeException: SSLv2Hello is disabled
> This only happens with networkConnections.  Regular client connections (such as the camel connector) work fine.
> Network Connection looks like:
> <networkConnection uri="static:(ssl://mybroker:61616)" />
> Example transportConnector that throws the error:
> <transportConnector name="openwire+ssl" uri="ssl://0.0.0.0:61616?transport.enabledProtocols=TLSv1,SSLv3" />
> Example transportConnector that does NOT error:
> <transportConnector name="openwire+ssl" uri="ssl://0.0.0.0:61616?transport.enabledProtocols=TLSv1,SSLv3,SSLv2Hello" />
> While the hello setting can be added, it shouldn't be needed.  Also, for compliance reasons, we need to be able to remove
> ALL support for SSLv2.
> Bigger question, why does this only happen for networkConnections?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira