I am in the process of walking through an ActiveMQ 6.3.0 install to observe the
differences and see what changes may or may not be required.
I run multiple brokers on a single instance/host and have not experienced any
issues.
Top create the configuration files need, I execute the following command:
$ACTIVEM_HOME/bin/activemq create $BROKER_CONF_LOCATION/$BROKER_NAME
When the command completes, I copy over the following raw files:
/conf/activemq.xml
All files and directories in /bin
Thes files withing these directories are then updated for each specific broker.
ActiveMQ Classic 6.3.0 still provides this option and I am able to perform the
same steps.
Walking through an installatioon and configuration I have noticed the following:
1 - If ACTIVEMQ_CONF in /bin/activemq is modified in any activemq fails to
load.
2 - If I set export ACTIVEMQ_CONF=/path/conf/BROKER_NAME activemq fails to
load
Here is the section within /bin/activemq that I have modified in the past:
# Active MQ configuration directory
if [ -z "$ACTIVEMQ_CONF" ] ; then
# For backwards compat with old variables we let ACTIVEMQ_CONFIG_DIR
set ACTIVEMQ_CONF
if [ -z "$ACTIVEMQ_CONFIG_DIR" ] ; then
ACTIVEMQ_CONF="${ACTIVEMQ_BASE%/}/conf"
else
ACTIVEMQ_CONF="$ACTIVEMQ_CONFIG_DIR"
fi
fi
The previous versions/release do not have this issue.
Is there a setting and/or flag that prevents the use of custom ACTIVEMQ_CONF
locations?
The option of updating and setting this in previous releases allows for brokers
to be completely independent.
Jason
