Queue subscribe: Calling thread is no longer blocked after connection failure about bunny

[olofheurgren]

Full script output from the above example (only difference is that port 5673 is used):

(main thread) BEFORE SUBSCRIBE
(subscribe thread) DURING SUBSCRIBE: message_1
W, [2021-11-17T15:52:22.130015 #345342]  WARN -- #<Bunny::Session:0x460 [email protected]:5673, vhost=/, addresses=[127.0.0.1:5673]>: Recovering from connection.close (CONNECTION_FORCED - broker forced connection closure with reason 'shutdown')
W, [2021-11-17T15:52:22.130281 #345342]  WARN -- #<Bunny::Session:0x460 [email protected]:5673, vhost=/, addresses=[127.0.0.1:5673]>: Will recover from a network failure (no retry limit)...
(main thread) AFTER SUBSCRIBE
W, [2021-11-17T15:52:32.133054 #345342]  WARN -- #<Bunny::Session:0x460 [email protected]:5673, vhost=/, addresses=[127.0.0.1:5673]>: Retrying connection on next host in line: 127.0.0.1:5673
(subscribe thread) DURING SUBSCRIBE: message_2

[michaelklishin]

Avoid blocking subscribes like a plague. It was a terrible feature to add (for ease of writing basic tutorials) that I deeply regret introducing.

I don't have the answer to your question; blocking forever is something that many would not like, you don't like the opposite behavior. As a library maintainer, you just cannot win.

Just use regular subscribes and block how you want, when you want.