[
https://issues.apache.org/jira/browse/NIFI-5639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18035455#comment-18035455
]
Will James commented on NIFI-5639:
----------------------------------
Hi, I am using the PublishAQMP processor in my flow and can confirm that this
is still an issue in NiFi 2.6.0.
Sending to a exchange/binding that doesn't exist still routes the FlowFile to
success, even though RabbitMQ ultimately rejects the message. This contradicts
the documentation for the processor which states that the _FlowFile will be
routed to the 'failure' relationship._
> PublishAMQP Processor
> -----------------------
>
> Key: NIFI-5639
> URL: https://issues.apache.org/jira/browse/NIFI-5639
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 1.5.0, 1.6.0, 1.7.0, 1.7.1
> Reporter: Mohammed Nadeem
> Assignee: Heiner León
> Priority: Critical
> Original Estimate: 96h
> Time Spent: 50m
> Remaining Estimate: 95h 10m
>
> *PublishAMQP* Processor is routing incoming flowfile to success relationship
> though invalid properties are configured. The processor is not throwing any
> errors when invalid properties are configured at run-time. When the message
> is not published with invalid properties, the processor silently routes the
> message to success when it is suppose to route to failure relationship
> indicating message was not published to the queue. This is a bug and no
> proper error handling when failures occur *(nifi-amqp-bundle)*
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
