You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Christopher L. Shannon (JIRA)" <ji...@apache.org> on 2017/06/08 16:24:18 UTC

[jira] [Created] (AMQ-6698) auto+nio+ssl protocolDetectionTimeout does not work if SSL handshake is not finished

Christopher L. Shannon created AMQ-6698:
-------------------------------------------

             Summary: auto+nio+ssl protocolDetectionTimeout does not work if SSL handshake is not finished
                 Key: AMQ-6698
                 URL: https://issues.apache.org/jira/browse/AMQ-6698
             Project: ActiveMQ
          Issue Type: Bug
          Components: Broker, Transport
    Affects Versions: 5.14.5
            Reporter: Christopher L. Shannon
            Assignee: Christopher L. Shannon
            Priority: Minor
             Fix For: 5.15.0, 5.14.6


The protocolDetectionTimeout value is supposed to define how long a connection attempt has to detect the protocol type before failing.  However there is a small issue where the initial SSL handshake is being done outside of the async task that times out.  This means that if the SSL handshake isn't finished because the client never sends enough bytes (such as if a client opens a normal TCP socket) then the socket will just hang open and not be closed.  The handshake should be moved inside of the task that times out to fix this.

Also, I'm going to change the default protocolDetectionTimeout to 30 seconds instead of 15 seconds as 30 is the default for the TcpTransport connectionTimeout value and also the default for the InactivityMonitor.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)