[
https://issues.apache.org/jira/browse/AMQ-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
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: https://issues.apache.org/jira/browse/AMQ-3042
> 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:
> ACTIVEMQ_HOSTNAME=`hostname`
> ACTIVEMQ_OPTS="-Denv.hostname=$ACTIVEMQ_HOSTNAME"
> The activemq.xml file that ships default could then read:
> <!--
> The <broker> element is used to configure the ActiveMQ broker.
> -->
> <broker xmlns="http://activemq.apache.org/schema/core";
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
