https://issues.apache.org/jira/browse/DISPATCH-55 would seem related.
You might also want to check https://issues.apache.org/jira/browse/QPID-6096 given this and your other mails. Robbie On 20 January 2017 at 08:45, Adel Boutros <adelbout...@live.com> wrote: > Hello, > > > I was messing around with the Dispatch Router and noticed a weird behavior. > > > If I start the dispatch router with a config file a first time, the broker is > started correctly and is available. > > If I start the same dispatch router a second time with the same config file, > it doesn't fail but in the logs it says the address is already bound but it > continues processing the config file. > > > Do you confirm that the second start should crash the dispatch router? > > > Logs on starting second dispatch router > > ---------------------------------------------------- > > Fri Jan 20 09:40:58 2017 DRIVER (error) bind: Address already in use > Fri Jan 20 09:40:58 2017 AGENT (debug) Add entity: > ListenerEntity(addr=0.0.0.0, authenticatePeer=False, cost=1, host=127.0.0.1, > identity=listener/127.0.0.1:10501, idleTimeoutSeconds=16, maxFrameSize=16384, > port=10501, requireEncryption=False, requireSsl=False, role=normal, > saslMechanisms=ANONYMOUS, stripAnnotations=both, > type=org.apache.qpid.dispatch.listener) > Fri Jan 20 09:40:58 2017 POLICY (info) Policy configured maximumConnections: > 0, policyFolder: '', access rules enabled: 'false' > Fri Jan 20 09:40:58 2017 AGENT (debug) Add entity: > Entity(defaultApplication=, defaultApplicationEnabled=False, > enableAccessRules=False, maximumConnections=0, policyFolder=, > type=org.apache.qpid.dispatch.policy) > .... > > > Regards, > > Adel --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org