Issue

We expect an exception to be thrown by a producer when no broker is available, as it does without discovery URL, using a single broker. Instead what you see is that an exception is not thrown, and the producer retries before failing without throwing an exception

We don't see this behavior in the fuse fabric mode, i.e. mq broker cluster in fabric and message producer in fabric or a generic java application. In this mode, the message producer hangs indefinitely and affects the whole application.

We expect to get an exception back in fabric mode as well. It doesn't matter what exception it is, Connection Refused, Timeout, etc. but a clear indication to the message producer that the message did not reach the queue and it is now the responsibility of the message producer application to deal with the situation.