I'm currently getting a number of test failures where a port passed in
by configuration is already in use. If the port specified is 0, then an
arbitrary port is selected if 4160 is not available.
However Reggie throws an exception during construction if a configured
port is in use.
I'd like
Only thing is, people do occasionally use unicast discovery. For instance, the
Amazon cloud doesn’t support multicast (that may have changed since I looked
into it). So in those cases, if you can’t come up on the chosen port, it is
actually a failure.
So I’d make the automatic failover featu
Ok, that makes sense I'll make it a property, that should fix the test
failures, the BindException will remain uncaught by default.
- Original message -
>
> Only thing is, people do occasionally use unicast discovery. For
> instance, the Amazon cloud doesn’t support multicast (that may
