[
https://issues.apache.org/jira/browse/ARTEMIS-2985?focusedWorklogId=511049&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-511049
]
ASF GitHub Bot logged work on ARTEMIS-2985:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 12/Nov/20 21:06
Start Date: 12/Nov/20 21:06
Worklog Time Spent: 10m
Work Description: gtully commented on pull request #3336:
URL: https://github.com/apache/activemq-artemis/pull/3336#issuecomment-726342326
the test failure was the result of adding a consumer without being fully
initialised.
server == null
see:
https://github.com/apache/activemq-artemis/pull/3336/files#diff-b56a3b568eccf7ca40814304ea1776eae27b1a4a2e5273cc2403470eae6414a3R257
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 511049)
Time Spent: 20m (was: 10m)
> 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)
