nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James McMahon <>
Subject Re: Nothing in rabbitMQ queue from Publish AMQP processor
Date Thu, 08 Dec 2016 16:41:16 GMT
Two quick updates. I generated a test message in the RMQ exchange using the
RabbitMQ Management Console. My goal was to see if the Idle and blocking
were problems or expected, and whether those would change when I sent a
test message to the queue. It's also a good validation that I've bound the
exchange and queue with a legit routing key. This worked - the test message
was delivered successfully.

I noticed that for each AMQP message nifi attempts to send to RMQ, RabbitMQ
Management Console creates a Connection that is shown with State of
blocking. and that is how it remains indefinitely. Nothing shows up in the
exchange or in the queue.


On Thu, Dec 8, 2016 at 8:26 AM, Oleg Zhurakousky <> wrote:

> Fair enough
> On Dec 8, 2016, at 8:16 AM, James McMahon <> wrote:
> I'm a captive audience in this respect. I do not have the latitude to
> change that, as it is dictated by a parent organization much broader than
> my level.
> On Thu, Dec 8, 2016 at 8:10 AM, Oleg Zhurakousky <
>> wrote:
>> James
>> Could you also see if you can upgrade to a newer version of NiFi? Current
>> release is 1.1.0, so 0.6.1 is about 3 releases behind and there were quite
>> a few bug fixes and improvements since then that could shed some more light
>> into your issue.
>> Meanwhile I’ll see what I can dig up on my end.
>> Cheers
>> Oleg
>> On Dec 8, 2016, at 8:00 AM, James McMahon <> wrote:
>> Yes absolutely Oleg. I will try to figure out how to make my rabbitMQ
>> queues explicitly active. I'll need to dig into that because it is not
>> plainly obvious to me how / if that needs to be done. I'll dig for that.
>> I am using NiFi 0.6.1.
>> Cheers and thanks again,
>> Jim
>> On Thu, Dec 8, 2016 at 7:46 AM, Oleg Zhurakousky <
>>> wrote:
>>> James I have not used AMQP in a while (although I am the one responsible
>>> for developing the functionality you’re having problem with ;)), so I need
>>> to brush up a bit on some of the administrative actions you describe (idle
>>> to active). Do i’ll get back to you, but as a joint debug step, can you
>>> please try to make your queens explicitly active and see if behavior
>>> changes?
>>> Also, what version of NiFi you are using?
>>> Cheers
>>> Oleg
>>> On Dec 8, 2016, at 7:37 AM, James McMahon <> wrote:
>>> Good morning and thank you Oleg. No, no other stack traces or errors are
>>> indicated. I've got my Publish AMQP configuration set to DEBUG for Bulletin
>>> Level.
>>> I do get an error at the UI when I try to Start the Publish AMQP step
>>> after I have Stopped it. It tells me "PublishAMQP[id=47f88.....744] cannot
>>> be started because it is not stopped. Current state is STOPPING". I suspect
>>> this is a reflection of the WARN log message.
>>> In your experience must I take some action at the RabbitMQ Management
>>> Console to change my Exchange and Queue from Idle to Active? I believe that
>>> would happen automatically when AMQP messages starting hitting the
>>> exchange, but I thought it best to ask. I see nothing on the management
>>> console that alludes to enabling the exchange or the queue.
>>> Jim
>>> On Thu, Dec 8, 2016 at 7:24 AM, Oleg Zhurakousky <
>>>> wrote:
>>>> James
>>>> Aside from “closing” failure message, do you see any other errors or
>>>> stack traces in the logs?
>>>> Meanwhile I’ll try to dig more with what I have?
>>>> Oleg
>>>> On Dec 8, 2016, at 7:13 AM, James McMahon <> wrote:
>>>> Hello I am trying to use a Publish AMQP step in my NiFi workflow. I
>>>> generate a flow file with random text content using Generate Flow File, and
>>>> then send to a rabbitMQ Exchange named nifiAbcX using Publish AMQP. My
>>>> exchange is bound to queue AbcQ by key **.Abc.**, and my virtual host
>>>> is nifiVhost. I have established my exchange as a Topic type.
>>>> My NiFi instance and my RabbitMQ instance are co-located for
>>>> development test purposes on the same server.
>>>> It appears that my Publish AMQP does indeed generate output which it
>>>> sends down the "success" output flow path, but at the RabbitMQ Management
>>>> Console I find that my Exchange and my Queue are Idle and show no messages.
>>>> My nifi log shows this Warning message: Failure while closing target
>>>> resource AMQPublisher:amqp://test@,
>>>> EXCHANGE:nifiAbcX,  What is this telling me?
>>>> Why am I seeing no messages posted to my rabbitMQ queue through the
>>>> exchange? Thank you in advance.

View raw message