You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Batuhan Bayrakçı (Jira)" <ji...@apache.org> on 2019/09/19 13:13: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=16933358#comment-16933358 ]
Batuhan Bayrakçı commented on NIFI-6312:
----------------------------------------
We have encountered with this situation. The problem was about the queue not exists nifi looking for to consume. After queue has been created, connection problem had been resolved.
> 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)