You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/08/03 16:44: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=17170177#comment-17170177 ]
ASF subversion and git services commented on NIFI-6312:
-------------------------------------------------------
Commit 7b4cce9e219b86e6c6ade357d57a5f9b87c5c70e in nifi's branch refs/heads/main from Peter Turcsanyi
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=7b4cce9 ]
NIFI-6312: Improved connection handling in AMQP processors
Disable connection automatic recovery which can lead to uncontrolled/stale threads. Handle the recovery in the processors instead.
Use poisoning in case of errors, then discarding and recreating the poisoned consumer/publisher.
NIFI-6312: Use conventional exception handling instead of poisoning
Use component logger in workers.
Remove basicNack()/basicReject() calls as they are not needed because all unacknowledged messages will be redelivered.
NIFI-6312: Further improve exception handling and error logging.
NIFI-6312: Fix consumer closing in previous commit
NIFI-6312: Use custom executor with a single thread (no more is used by the processor)
Reviewed by tamas palfy and simon bence
Signed-off-by: Joe Witt <jo...@apache.org>
> 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
> Time Spent: 1.5h
> 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)