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.
Kind Regards, Alex On 16 May 2016 at 16:12, Gordon Sim <[email protected]> wrote: > On 12/05/16 16:41, Keith W wrote: >> >> A release candidate for the next release (6.0.3) of the Qpid Java >> Components has been created. >> >> The list of changes can be found in Jira: >> >> >> https://issues.apache.org/jira/issues/?jql=project%20%3D%20QPID%20AND%20fixVersion%20%3D%20qpid-java-6.0.3 >> >> Please test and vote accordingly. >> >> The source and binary archives can be grabbed from here: >> https://dist.apache.org/repos/dist/dev/qpid/java/6.0.3-rc1 > > > Built packages including tests which all past. Installed the produced binary > zip file and started broker. Ran qpid::messaging against it over both AMQP > 0-10 and 1.0, through a queue and amq.fanout; all passed successfully. Ran > proton python examples against it, which also passed (client-server example > doesn't pass as it uses an 'anonymous' sender in the service with address > set on 'to' field). > > One minor point, just in case it hasn't been previously raised (and > certianly not a blocker), the broker doesn't give any error message if it > fails to bind to the 5672 port on startup (e.g. if something else is > listening on that port). > > > --------------------------------------------------------------------- > 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]
