This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • ZeroConf Transport Reference
Skip to end of metadata
Go to start of metadata

The ZeroConf Transport

The ZeroConf transport works just like Discovery Transport, except that it uses a ZeroConf based discovery agent to locate the list of broker uris to connect to.

Configuration Syntax

zeroconf:serviceName?transportOptions
or
zeroconf:serviceName

where serviceName is the Zeroconf service name; which seems to start with an underscore (_) and must end with a dot (.). So we can use this service name to distinguish development, UAT & production brokers - or group them into domains etc.

Note that to be able to use ZeroConf to find brokers, the brokers need to have Discovery enabled. To configure discovery in a Broker you should use the Xml Configuration. Its basically something like...

<broker name="foo">
  <transportConnectors>
    <transportConnector name="openwire" uri="tcp://0.0.0.0:61616" discoveryUri="zeroconf:_activemq_development. />
  </transportConnectors>
  ...
</broker>
Example client URI
zeroconf:_activemq_development.
  • No labels