If possible, can somebody help me understand why using `block: true` option is bad for blocking the main thread? It is quite convenient if your application just a consumer of the queue and you need to start it and keep the main thread alive.
Also what are the alternative possibilities for doing this without `block: true`?
Thanks in advance!
Evgeniy Fateev
unread,
Jun 15, 2020, 6:31:48 AM6/15/20
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Ruby RabbitMQ libraries
Looks like `loop { sleep 1 }` is a straightforward way to keep main thread alive.
But still curious about `block: true` considerations.
Michael Klishin
unread,
Jun 24, 2020, 5:46:28 PM6/24/20
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Ruby RabbitMQ libraries
It does not work well with automatic connection recovery. There is no easy way to cancel such consumer.
It's just too limited to be useful beyond basic tutorials and experiments.