[
https://issues.apache.org/jira/browse/AMQ-6535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15742364#comment-15742364
]
ASF subversion and git services commented on AMQ-6535:
------------------------------------------------------
Commit 27238b2dd790cea38d95da46b23ed141f5847782 in activemq's branch
refs/heads/master from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=27238b2 ]
https://issues.apache.org/jira/browse/AMQ-6535
Fixing the auto+nio+ssl transport so that the protocol detection task
will properly terminate on timeout and not continue to run. Also
lowered the default detection timeout to 15 seconds instead of 30
seconds to match the InactivityMonitor default.
> auto+nio+ssl transport protocol detection task doesn't always terminate
> -----------------------------------------------------------------------
>
> Key: AMQ-6535
> URL: https://issues.apache.org/jira/browse/AMQ-6535
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.14.2
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
>
> There's an issue with the auto+nio+ssl transport where the task that runs to
> read enough byets to detect the protocol can continue to run even after the
> timeout period. This ends up eating up cpu and the task will never stop.
> This can happen if there's a repeated exception when trying to read from the
> protocol or when the client connects but doesn't send enough bytes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
