[
https://issues.apache.org/jira/browse/NIFI-15483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Turcsanyi resolved NIFI-15483.
------------------------------------
Fix Version/s: 2.10.0
Resolution: Fixed
> PublishAMQP doesn't route on publish failure
> --------------------------------------------
>
> Key: NIFI-15483
> URL: https://issues.apache.org/jira/browse/NIFI-15483
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 2.6.0
> Environment: RHEL 9, NiFi 2.6.0 + RabbitMQ 4.2
> Reporter: Will James
> Assignee: Rakesh Kumar Singh
> Priority: Critical
> Fix For: 2.10.0
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> The issue from NIFI-5639 still persists in NiFi v2. Essentially, If you
> attempt to publish a message using PublishAMQP using invalid properties (e.g.
> incorrect exchange name or user permission), the message would fail to
> publish but will still go to the 'success' relationship. This contradicts
> the PublishAMQP documentation for the the failure relationship: '{_}All
> FlowFiles that cannot be routed to the AMQP destination are routed to this
> relationship.'{_}
> Steps to reproduce:
> # Set up a *PublishAMQP* processor that successfully publishes to a RabbitMQ
> queue
> # Change the _*Exchange Name*_ property on the *PublishAMQP* to an exchange
> that doesn't exist in RabbitMQ.
> # Send a valid flow file to the *PublishAMQP* processor. RabbitMQ will fail
> to process the message, but NiFi still routes it to 'success'. Depending on
> the configuration of RabbitMQ, there may be an error bulletin on the NiFi
> processor. I've seen this happen when publishing using a user with limited
> queue/exchange permissions - NiFi shows a permission denied response and
> still routes to success.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
