Wanted to follow up in case it serves others in the future. I stepped through these changes before I got this to work:
1. My associate extended the heartbeat on the RMQ host. 2. I made two changes to NiFi's bootstrap.conf, restarting NiFi after editing the file to pick up these changes: ..... java.arg.X=-Dcom.rabbitmq.client.heartbeat=120 ..... java.arg.X=-Dcom.rabbitmq.client.connection_timeout=30000 3. I had experimented with settings on a few properties in ConsumeAMQP 2.0.0-M2. It works with these set as follows: ..... Auto-Acknowledge Messages false ..... Prefetch Count 1 On Fri, Jul 5, 2024 at 1:28 PM James McMahon <jsmcmah...@gmail.com> wrote: > I have a queue in RabbitMQ that I try to ConsumeAMQP from, configured like > this: > > Queue > detection-responses > Auto-Acknowledge Messages > false > Batch Size > 1 > Prefetch Count > 0 > Header Output Format > Comma-Separated String > Header Separator > , > Remove Curly Braces > False > BrokersNo value setHost Name > 18.235.119.166 > Port > 5672 > Virtual Host > / > User Name > Admin > Password Sensitive value > setAMQP Version > 0.9.1 > SSL Context Service > No value set > Use Client Certificate Authentication > false > > My messages are not successfully consumed into my nifi flow. This is what > I find in my log: > > 17:23:39 UTC > INFO > 1134134d-1ec5-158c-c3db-526be43cd3fa > > ConsumeAMQP[id=1134134d-1ec5-158c-c3db-526be43cd3fa] Successfully connected > AMQPConsumer to amqp://Admin@18.235.119.166:5672/ and 'detection-responses' > queue > > 17:23:39 UTC > DEBUG > 1134134d-1ec5-158c-c3db-526be43cd3fa > > ConsumeAMQP[id=1134134d-1ec5-158c-c3db-526be43cd3fa] Closing AMQP channel for > amqp://Admin@18.235.119.166:5672/ > > 17:23:39 UTC > INFO > 1134134d-1ec5-158c-c3db-526be43cd3fa > > ConsumeAMQP[id=1134134d-1ec5-158c-c3db-526be43cd3fa] Consumer is closed, > discarding message (delivery tag: 1). > > Auto-refresh > > > > Is this because the channel is closing prematurely? Is there a queue > property I must set to keep it open? > > Thank you for any help. >
