Handling long running tasks in pika / RabbitMQ

by

For now, your best bet is to turn off heartbeats, this will keep RabbitMQ from closing the connection if you’re blocking for too long. I am experimenting with pika’s core connection management and IO loop running in a background thread but it’s not stable enough to release.

In pika v1.1.0 this is ConnectionParameters(heartbeat=0)

More Related Contents:

  1. Can’t access RabbitMQ web management interface after fresh install
  2. Spring AMQP + RabbitMQ 3.3.5 ACCESS_REFUSED – Login was refused using authentication mechanism PLAIN
  3. RabbitMQ 3.3.1 can not login with guest/guest
  4. ActiveMQ or RabbitMQ or ZeroMQ or [closed]
  5. RabbitMQ – Message order of delivery
  6. RabbitMQ / AMQP: single queue, multiple consumers for same message?
  7. RabbitMQ and relationship between channel and connection
  8. How do I set a number of retry attempts in RabbitMQ?
  9. Spring RabbitMQ – using manual channel acknowledgement on a service with @RabbitListener configuration
  10. When to use RabbitMQ over Kafka? [closed]
  11. Is there a performance difference between pooling connections or channels in rabbitmq?
  12. How to add initial users when starting a RabbitMQ Docker container?
  13. RabbitMQ fails on Error: unable to connect to node rabbit@TPAJ05421843: nodedown
  14. Service Oriented Architecture – AMQP or HTTP
  15. Getting number of messages in a RabbitMQ queue

Leave a Comment