[ https://issues.apache.org/jira/browse/NIFI-6312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853265#comment-16853265 ]
Joseph Witt commented on NIFI-6312: ----------------------------------- this comment is interesting https://github.com/rabbitmq/rabbitmq-java-client/blob/v5.6.0/src/main/java/com/rabbitmq/client/impl/recovery/AutorecoveringConnection.java#L612-L615 > 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)