I'm using amqp-coffee with reconnect = false option. Below is an example that reproduces the issue I faced recently. The example is a simple producer that publishes new message every second:
Expected result:
Option 1. For all next publishes the callback is invoked with an error
Option 2. The process crashes because of unhandled exception
Actual result:
Next publishes hang forever. Callbacks are never called. As I understand, publish waits until connection is back, but since reconnect is disabled it never happens.
Hi,
I'm using amqp-coffee with
reconnect = false
option. Below is an example that reproduces the issue I faced recently. The example is a simple producer that publishes new message every second:The scenario is following:
Expected result: Option 1. For all next publishes the callback is invoked with an error Option 2. The process crashes because of unhandled exception
Actual result: Next publishes hang forever. Callbacks are never called. As I understand, publish waits until connection is back, but since
reconnect
is disabled it never happens.What do you think?