[
https://issues.apache.org/jira/browse/NIFI-6312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853369#comment-16853369
]
Joseph Witt commented on NIFI-6312:
-----------------------------------
reviewing this part of the doc suggests disabling recovery is important given
how we have our logic established
https://www.rabbitmq.com/api-guide.html#connection-recovery
trying that now
> 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)
