activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dimos Raptis <>
Subject Propagation of failure of broker to bind to an address
Date Wed, 14 Oct 2020 10:58:35 GMT

We are working on upgrading our dependency on artemis-server from version 2.6.2 to 2.15.0.
We have 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 an 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.
For some more context, I actually managed to track down the ticket that introduced this change
in behaviour, which is this one:

Could someone confirm if this is a bug or the intended behaviour?

Thank you,

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message