[
https://issues.apache.org/activemq/browse/AMQ-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dejan Bosanac resolved AMQ-2975.
--------------------------------
Resolution: Fixed
Fixed with svn revision 1022475
> New shell scripts doesn't work well with multiple broker instances
> ------------------------------------------------------------------
>
> Key: AMQ-2975
> URL: https://issues.apache.org/activemq/browse/AMQ-2975
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.4.1
> Reporter: Dejan Bosanac
> Assignee: Dejan Bosanac
> Fix For: 5.5.0
>
>
> 1) Create the instances:
> $ cd /home/phil/apache-activemq-5.4.1
> $ bin/activemq create broker1
> $ bin/activemq setup ~/.activemqrc-instance-broker1
> $ ln -s activemq bin/activemq-instance-broker1
> $ bin/activemq create broker2
> $ bin/activemq setup ~/.activemqrc-instance-broker2
> $ ln -s activemq bin/activemq-instance-broker2
> 2) set unique ports for the instances in their conf/activemq.xml and
> conf/jetty.xml files as shown below:
> $ grep 16 broker[12]/conf/*.xml
> broker1/conf/activemq.xml: <transportConnector name="openwire"
> uri="tcp://0.0.0.0:61616"/>
> broker1/conf/jetty.xml: <property name="port" value="8161"
> />
> broker2/conf/activemq.xml: <transportConnector name="openwire"
> uri="tcp://0.0.0.0:61626"/>
> broker2/conf/jetty.xml: <property name="port" value="8162"
> />
> When I try to start both brokers, I get a "Process with pid XXX is already
> running" message. This is due to the pid file being created in
> $ACTIVEMQ_HOME/data rather than the instance's $ACTIVEMQ_BASE/data directory
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
