OK - On trunk I've added some extra logging which should help. I also (still) think we should default to enabling "failStartupWithErroredChild", or - as per Robbie's suggestion - failing if any ports are errored (though annoyingly currently HTTP ports are not errored - it is the plugin which fails).
-- Rob On 16 May 2016 at 17:14, Gordon Sim <[email protected]> wrote: > On 16/05/16 16:31, Oleksandr Rudyy wrote: > >> Hi Gordon, >> >> Java broker has a context variable broker.failStartupWithErroredChild >> (set to false by default) to control whether broker should fail or >> continue running on any issue on startup. >> If you start broker using >> $BROKER_HOME/bin/qpid-server -prop broker.failStartupWithErroredChild=true >> it should fail when port is bound. >> > > It does indeed.... (though if I remember to start with that next time, > I'll most likely also remember to check nothing else is using the port :-) > > Just to continue with some nit-picking, the error message isn't entirely > obvious: > > [Broker] BRK-1016 : Fatal error : Broker context variable >> broker.failStartupWithErroredChild is set and the broker has ERRORED >> children : See log file for more information >> > > Looking through the log file I see: > > 2016-05-16 17:06:27,820 WARN [Broker-Config] (o.a.q.s.m.a.BrokerAdapter) >> - Broker child object 'AMQP' of type 'Port' is ERRORED >> 2016-05-16 17:06:27,822 ERROR [Broker-Config] >> (o.a.q.s.m.AbstractConfiguredObject) - Failed to open object with name >> 'Broker'. Object will be put into ERROR state. >> > > which is better, but still not entirely obvious (at least to me) unless > you know what the problem was to begin with. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
