You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Pierre Villard (Jira)" <ji...@apache.org> on 2026/01/05 10:36:07 UTC

[jira] [Resolved] (NIFI-4463) MQTT client disconnection in ConsumeMQTT Processor

     [ https://issues.apache.org/jira/browse/NIFI-4463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pierre Villard resolved NIFI-4463.
----------------------------------
    Resolution: Feedback Received

Apache NiFi 1.x is no longer maintained and no new release is planned on the 1.x release line. Marking as resolved as part of a cleanup operation. Please open a new one with an updated description if this is still relevant for NiFi 2.x.

> MQTT client disconnection in ConsumeMQTT Processor
> --------------------------------------------------
>
>                 Key: NIFI-4463
>                 URL: https://issues.apache.org/jira/browse/NIFI-4463
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 1.3.0
>         Environment: OS: Centos /
> MQTT Borker: mosquitto
>            Reporter: Stefano Melzi
>            Priority: Minor
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> When internal queue is full the messageArrived method throws an exception causing the MQTT client to disconnect. This event is managed creating a new client which try to reconnect to the broker.
> In our test using a mosquitto broker with a high mqtt traffic and a low value for "Max Queue Size" property we experiment broker disconnection when internal queue is full, but after this event MQTT Processor remains blocked without any attempt to reconnect.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)