activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] [Commented] (AMQ-5598) MQTT+NIO+SSL: Concurrent connections lead to 100% CPU usage
Date Sat, 07 Mar 2015 13:25:38 GMT


Timothy Bish commented on AMQ-5598:

No, the MQTT code does not move through the AMQP code.  There are issues with the legacy AMQP
1.0 JMS client that we use for testing, some of which are fixed in the upcoming 0.32 release
but in general that client is not heavily maintained or tested.  The is a new one in the works
that myself and [~gemmellr] are working on which will be compliant with the JMS over AMQP
mapping spec we are also working on.  Once there is an initial release of that we will probably
switch ActiveMQ to using that in its tests to resolve those problems. 

> MQTT+NIO+SSL: Concurrent connections lead to 100% CPU usage
> -----------------------------------------------------------
>                 Key: AMQ-5598
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: MQTT
>    Affects Versions: 5.10.0, 5.11.0
>         Environment: Red Hat Enterprise Linux Server release 6.6 (Santiago), Open JDK
64bit, 3Gig RAM, 30Gig HDD - 1x ActiveMQ 5.10
> Windows 7 x64, Java 64bit 1.7.0, 8Gig RAM, 1x ActiveMQ 5.10, 1x ActiveMQ 5.11
>            Reporter: Josef Awad
>              Labels: performance, security
>         Attachments: Screen Shot 2015-02-12 at 8.31.58 PM.png
> Connecting with multiple instances of  mqtt clients via ssl at the same time causes the
borker server to run on 100% CPU usage forever. Only restart of ActiveMQ helps. Thread count
maximizes during connection attempt.
> Critical: It doesn't matter if the certificate is valid or not, I am able to shut down
the broker from one client with 500 concurrent connecting instances. The payload size is not
important. The problem is somewhere at the ssl handshake located. Without ssl everything works
fine. Single ssl connections work.
> Similar issues (with older versions) described are here:
> -
> -

This message was sent by Atlassian JIRA

View raw message