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 subversion and git services (Jira)" <ji...@apache.org> on 2020/11/13 02:18:00 UTC
[jira] [Commented] (ARTEMIS-2985) MQTT should not block netty
thread
[ https://issues.apache.org/jira/browse/ARTEMIS-2985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231104#comment-17231104 ]
ASF subversion and git services commented on ARTEMIS-2985:
----------------------------------------------------------
Commit 9675ecae428d85126429418de544d3a547229f19 in activemq-artemis's branch refs/heads/master from gtully
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=9675eca ]
ARTEMIS-2985 - don't block netty threads for mqtt protocol actions
> MQTT should not block netty thread
> ----------------------------------
>
> Key: ARTEMIS-2985
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2985
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: MQTT
> Affects Versions: 2.16.0
> Reporter: Gary Tully
> Assignee: Gary Tully
> Priority: Major
> Fix For: 2.17.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> If some mqtt op blocks on the address or binding manager it will block the netty threads and starve existing consumers. In the same way that openwire (ARTEMIS-2685) delegates to an ordered executor, mqtt needs to do the same.
> it can leave the ping response in netty to ensure connections stay open while busy.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)