activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Davies (Resolved) (JIRA)" <>
Subject [jira] [Resolved] (AMQ-3042) Default broker name to be machine's hostname
Date Sat, 14 Apr 2012 05:48:21 GMT


Rob Davies resolved AMQ-3042.

       Resolution: Fixed
    Fix Version/s: 5.6.0
         Assignee: Rob Davies

Don't set the brokerName in the configuration file and set the broker property: useLocalHostBrokerName=true
will achieve this
> Default broker name to be machine's hostname
> --------------------------------------------
>                 Key: AMQ-3042
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.4.1
>            Reporter: James Green
>            Assignee: Rob Davies
>            Priority: Trivial
>             Fix For: 5.6.0
> In many scenarios, including ours, there is one AMQ broker per host. They connect to
each other but must have unique brokerName values.
> It would therefore make sense to send into AMQ at launch the current hostname and refer
to this for the value instead of the literal value "localhost".
> This would lend itself to invoking lots of new broker hosts within a virtualised environment
with reduced configuration work.
> The init.d script could have two lines added:
> The activemq.xml file that ships default could then read:
>     <!--
>         The <broker> element is used to configure the ActiveMQ broker.
>     -->
>     <broker xmlns="" brokerName="${env.hostname}"
dataDirectory="${activemq.base}/data" destroyApplicationContextOnStop="true">
> Unsure about other platforms but that works for linux.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message