Dimos Raptis created ARTEMIS-2950:
-------------------------------------
Summary: Failure of a broker to bind to an address is not
propagated
Key: ARTEMIS-2950
URL: https://issues.apache.org/jira/browse/ARTEMIS-2950
Project: ActiveMQ Artemis
Issue Type: Bug
Affects Versions: 2.15.0
Reporter: Dimos Raptis
While working on an upgrade of our dependency on {{artemis-server}} from
version 2.6.2 to 2.15.0, we noticed that while a failure to bind on an address
was propagating to the client before, in the newer version it does not
propagate anymore.
More specifically, we are making use of the API {{ActiveMQServerImpl.start()}}
that was previously throwing a netty {{NativeIoException}}, but now it is
swallowing it and only logging an error instead. We are making use of this
exception to react to the failure to bind and we have some automated tests
around it that started failing during the upgrade. Our tests are working in the
following way:
* We first bind a socket to a specific port.
* Then, we attempt to start a broker on the same port.
* The expectation of the test is that the start() operation will fail with an
exception.
To provide some more context, I managed to track down the ticket that
introduced this change in behaviour, which is this one:
https://issues.apache.org/jira/browse/ARTEMIS-2106
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
