You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/03/11 13:06:00 UTC

[jira] [Work logged] (ARTEMIS-1604) Artemis deadlock using MQTT Protocol

     [ https://issues.apache.org/jira/browse/ARTEMIS-1604?focusedWorklogId=210967&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-210967 ]

ASF GitHub Bot logged work on ARTEMIS-1604:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 11/Mar/19 13:05
            Start Date: 11/Mar/19 13:05
    Worklog Time Spent: 10m 
      Work Description: franz1981 commented on pull request #2577: ARTEMIS-1604 Artemis deadlock using MQTT Protocol
URL: https://github.com/apache/activemq-artemis/pull/2577
 
 
   Direct and async deliveries lock QueueImpl::this and
   ServerConsumerImpl::this in different order causing deadlock:
   has been introduced a deliverLock to prevent both type of delivers
   to concurrently happen, making irrelevant the lock ordering.
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 210967)
            Time Spent: 10m
    Remaining Estimate: 0h

> Artemis deadlock using MQTT Protocol
> ------------------------------------
>
>                 Key: ARTEMIS-1604
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1604
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>            Reporter: Tiago Santos
>            Priority: Major
>         Attachments: artemisDeadlock.log, artemis_thread_dump.log, broker.xml
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Hello,
> When load testing artemis as our MQTT Broker, we detected the broker deadlocks and crashs (see attached log).
> Our use case is trying 1000 simultaneous connections (publishers) each sending 1 message per second with 1KB size.
> After all 1000 clients successfully connected to artemis and start sending the messages after a while the deadlock comes up.
> The Xms and Xmx of the JVM both are set to 4GB
> The broker.xml can be found in attach.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)