Oh sorry, I misunderstood. Yes indeed we have already tested these features on the broker.
________________________________ From: Robbie Gemmell <[email protected]> Sent: Friday, January 20, 2017 12:00:22 PM To: [email protected] Subject: Re: [Dispatch Router] Unexpected behavior when starting the same dispatch router twice On 20 January 2017 at 10:24, Adel Boutros <[email protected]> wrote: > Thank you Robbie, > > > Regarding DISPATCH-55, is it possible to include it in a patch release if > 0.8.0 is still far from being released? > I'm not sure when 0.8.0 is due (though it has been a reasonable time since 0.7.0 now..), so I'll need to defer that to Ted. > > However, I don't see how QPID-6096 is related to my other question. > > Imagine I have a script which launches the Qpid Java Broker and doesn't > continue until the broker is started. I can do it by parsing the console and > waiting for the message "Broker is ready". My question was actually how can I > do it for the dispatch router? I couldn't find a log line which says for > example "Dispatch router is ready". > I wasn't referring to that question specifically, just your use of the broker in general. If you read the JIRA or give it a try then, unless its changed and I've missed it, you'll see that by default the Java broker also only logs about the port conflict. > > Regards, > > Adel > > ________________________________ > From: Robbie Gemmell <[email protected]> > Sent: Friday, January 20, 2017 10:52:48 AM > To: [email protected] > Subject: Re: [Dispatch Router] Unexpected behavior when starting the same > dispatch router twice > > 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 <[email protected]> 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: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
