In the Java Broker the definition of "ready" is kind of recursive... it is ready if all the objects it "manages" are ready... and they are ready if all the objects they manage are ready... etc.
In practice this means that the when the Broker is ready, all the virtual hosts have completed recovery (either they are up, or in REPLICA mode, or potentially there were configuration errors that have been reported in the logs), all the ports are open and accepting connections,... etc... -- Rob On 20 January 2017 at 14:31, Adel Boutros <[email protected]> wrote: > Thank you Ted. > > > I agree the definition of ready can have many interpretations. > > > What is the case for the Java Broker? > > > I assume that when the broker or the dispatcher are ready, I can start > sending/receiving messages as well as configuring them either via the rest > API or the qdmanage/qdstat tools. > > > Regards, > > Adel > > ________________________________ > From: Ted Ross <[email protected]> > Sent: Friday, January 20, 2017 2:12:23 PM > To: [email protected] > Subject: Re: [Dispatch Router] How to know the Dispatch Router is ready > > Adel, > > There's probably some interesting conversation we could have around what > you mean by "ready". That said, when the following log line is issued, > the router is initialized and open for business. > > SERVER (info) Operational, # Threads Running > > If you are using a network of routers, the routers will start > synchronizing with each other _after_ that log is issued. > > -Ted > > On 01/20/2017 03:27 AM, Adel Boutros wrote: > > Hello, > > > > > > For the Qpid Java Broker, a message is outputted on the console saying > the broker is ready ([Broker] BRK-1004 : Qpid Broker Ready). > > > > Is there something equivalent for the Dispatch Router? > > > > > > Regards, > > > > Adel > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
