[
https://issues.apache.org/jira/browse/NIFI-5721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16654139#comment-16654139
]
Aldrin Piri commented on NIFI-5721:
-----------------------------------
Attached a log of the problem occurring. This was generated by using a docker
container running MQTT via:
{code:bash}
docker run -it -p 1883:1883 -p 9001:9001 eclipse-mosquitto
{code}
A flow of two identically configured ConsumeMQTT processors (inclusive of
Client ID) feeding a LogAttribute was used to draw out the error condition
believed to be in https://github.com/eclipse/paho.mqtt.java/issues/474 as
suggested by https://github.com/eclipse/paho.mqtt.java/issues/429
> ConsumeMQTT processor can exhaust system threads
> ------------------------------------------------
>
> Key: NIFI-5721
> URL: https://issues.apache.org/jira/browse/NIFI-5721
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Aldrin Piri
> Priority: Major
> Fix For: 1.7.1
>
> Attachments: nifi-app-oome.log
>
>
> Originally reported on the mailing list as a MiNiFi issue,
> https://lists.apache.org/thread.html/d64afc392d8c503997634ed4e9285ba4e89ccc83002e99c66d259c89@%3Cusers.nifi.apache.org%3E.
> After some initial evaluation it appears there is a bug being triggered in
> the mqtt library that is not being handled by NiFi and causing a resource
> leak.
> Original thread here:
> https://lists.apache.org/thread.html/d64afc392d8c503997634ed4e9285ba4e89ccc83002e99c66d259c89@%3Cusers.nifi.apache.org%3E
> Additional details to follow as I evaluate how to trigger it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
