You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Robert Bruno (JIRA)" <ji...@apache.org> on 2019/06/01 11:40:00 UTC
[jira] [Commented] (NIFI-6312) AMQP processors seem to have thread
cleanup issues
[ https://issues.apache.org/jira/browse/NIFI-6312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853673#comment-16853673 ]
Robert Bruno commented on NIFI-6312:
------------------------------------
Thanks so much for looking at this! Let me know if that setting seems to be the key. If so I will for sure recompile with it disabled. If you don't have time to test, I should next week.
> AMQP processors seem to have thread cleanup issues
> --------------------------------------------------
>
> Key: NIFI-6312
> URL: https://issues.apache.org/jira/browse/NIFI-6312
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.9.0
> Reporter: Robert Bruno
> Priority: Major
>
> At a minimum the ConsumeAMQP processor exhibits this behavior but the PublishAMQP may as well.
> If ConsumeAMQP is listening to a working AMQP server and then that server name is no longer resolvable errors begin to show up in logs saying the hostname can't be resolve. This is expected.
> What isn't expected is if you then turn off the processor or even delete the processor the error message persists. The only way to resolve this is restarting the nifi node.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)