Hi Rob, Thank you for your answer. Yes, it really helps!
Regards, Antoine -----Original Message----- From: Rob Godfrey [mailto:[email protected]] Sent: mercredi 1 février 2017 15:22 To: [email protected] Subject: Re: Http management port already in use for Qpid Java Broker 6.0.4 Hi Antoine, what we did in QPID-6906 is make everything consistent, that is if you don't set the System property / Broker context variable "broker.failStartupWithErroredChild" to true, then the broker simply logs the fact that children have been misconfigured or can't open sockets. Prior to the change in that JIRA the behaviour was different between HTTP ports and AMQP ports, which didn't make much sense. For 6.1 I don't think there is a way to fix the management port after the broker has started, you'll need to stop/start the broker. In 7.0 you'll be able to use AMQP management to update state / perform a restart from management. If you want the broker to fail in the case of a port not being opened, or any other failure in the broker's direct children, (and personally I think is the sensible choice, and probably should be the default) then you need to set the "broker.failStartupWithErroredChild" to true System Property / context variable to true. Hope this helps, Rob On 1 February 2017 at 15:10, Antoine Chevin <[email protected]> wrote: > Hello, > > I noticed that when starting the Qpid Java Broker with the management > port already in use, it logs that it could not start the service and > then that the broker is ready. > > I've read https://issues.apache.org/jira/browse/QPID-6096 and I'm > wondering why the http management port isn't a special case? > How can it be restarted without a broker restart? > > Thanks in advance, > Regards, > Antoine >
