[ https://issues.apache.org/jira/browse/NIFI-6312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16933365#comment-16933365 ]
Joseph Witt commented on NIFI-6312: ----------------------------------- In my review of the code for this processor and interaction with a proper AMQP server I believe this processor requires significant rework. It is useable for some cases but it needs to be largely rewritten. > 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 (v8.3.4#803005)