[
https://issues.apache.org/jira/browse/AMQ-6505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15677219#comment-15677219
]
ASF subversion and git services commented on AMQ-6505:
------------------------------------------------------
Commit 3903ea08ab699ab01d98a13524cdfc9fd01159b3 in activemq's branch
refs/heads/activemq-5.14.x from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=3903ea0 ]
https://issues.apache.org/jira/browse/AMQ-6505
Fix compilation error on 5.14.x branch
> Auto transports can lead to high cpu usage and failed connections under high
> load
> ---------------------------------------------------------------------------------
>
> Key: AMQ-6505
> URL: https://issues.apache.org/jira/browse/AMQ-6505
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.14.1
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
> Fix For: 5.15.0, 5.14.2
>
>
> There's an issue with the auto transports that can cause failed connections
> and very high cpu usage when there is a high number of concurrent connections
> attempted at the same time. I noticed this primarily under load testing the
> auto+nio+ssl transport. After some debugging, it turns out the issue is the
> ByteBuffer that is used to capture the initial bytes for protocol detection.
> The buffer should be local per thread and not shared but by mistake it was
> made a class level variable so under high load and contention the buffer can
> be manipulated by more than one thread causing failures and high cpu load
> (especially under NIO)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
