[ https://issues.apache.org/jira/browse/NIFI-6312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Witt updated NIFI-6312: --------------------------- Resolution: Fixed Status: Resolved (was: Patch Available) +1 merged to main > 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 > Assignee: Peter Turcsanyi > Priority: Major > Fix For: 1.12.0 > > Time Spent: 1h 50m > Remaining Estimate: 0h > > 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)