[ https://issues.apache.org/activemq/browse/AMQ-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Scott Clasen updated AMQ-2306: ------------------------------ Description: It appears that when running in shared master slave configuration one cant connect to the jmx console or user activemq-admin to stop the slave. Start a slave with a master running ACTIVEMQ_HOME: /itdept/apache-activemq-5.2.0 ACTIVEMQ_BASE: /itdept/apache-activemq-5.2.0 Loading message broker from: xbean://itdept//messagebroker/activemq-config/broker3.xml INFO BrokerService - Using Persistence Adapter: AMQPersistenceAdapter(/datafiles/itdept//activemq-journal) WARN AMQPersistenceAdapter - Waiting to Lock the Store /datafiles/itdept/activemq-journal Notice that no connections including jmx have been started...attempts to stop the broker with activemq-admin fail with..Caused by: java.net.ConnectException: Connection refused Kill the master and get INFO AMQPersistenceAdapter - Aquired lock for AMQ Store/datafiles/itdept/activemq-journal INFO BrokerService - ActiveMQ 5.2.0 JMS Message Broker (messagebroker3) is starting INFO BrokerService - For help or more information please see: http://activemq.apache.org/ INFO KahaStore - Kaha Store using data directory /datafiles/itdept/activemq-journal/kr-store/data INFO ManagementContext - JMX consoles can connect to service:jmx:rmi:///jndi/rmi://localhost:55563/jmxrmi INFO TransportServerThreadSupport - Listening for connections at: tcp://0.0.0.0:55553 INFO TransportConnector - Connector tcp Started INFO BrokerService - ActiveMQ JMS Message Broker (messagebroker3, ID:nymb02d-59998-1245957027403-0:0) started INFO log - Logging to org.slf4j.impl.JCLLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog INFO log - jetty-6.1.9 INFO log - web...@1288520654 at http://0.0.0.0:55573/admin INFO log - Started selectchannelconnec...@0.0.0.0:55573 Now you can connect via JMX and concole.... brokers are very simply configured... broker3 <broker:broker useJmx="true" persistent="true" brokerName="messagebroker3"> <broker:managementContext> <broker:managementContext connectorPort="55563" jmxDomainName="messagebroker3"/> </broker:managementContext> <broker:persistenceAdapter> <broker:amqPersistenceAdapter directory="/datafiles/itdept/activemq-journal"/> </broker:persistenceAdapter> <broker:transportConnectors> <broker:transportConnector name="tcp" uri="tcp://0.0.0.0:55553"/> </broker:transportConnectors> </broker:broker> broker 4 <broker:broker useJmx="true" persistent="true" brokerName="messagebroker4"> <broker:managementContext> <broker:managementContext connectorPort="55564" jmxDomainName="messagebroker4"/> </broker:managementContext> <broker:persistenceAdapter> <broker:amqPersistenceAdapter directory="/datafiles/itdept/activemq-journal"/> </broker:persistenceAdapter> <broker:transportConnectors> <broker:transportConnector name="tcp" uri="tcp://0.0.0.0:55554"/> </broker:transportConnectors> </broker:broker> was: It appears that when running in shared master slave configuration one cant connect to the jmx console or user activemq-admin to stop the slave. Start a slave with a master running > Unable to monitor or manage slave brokers in shared filesystem master slave > configuration > ----------------------------------------------------------------------------------------- > > Key: AMQ-2306 > URL: https://issues.apache.org/activemq/browse/AMQ-2306 > Project: ActiveMQ > Issue Type: Bug > Components: Broker, JMX > Affects Versions: 5.2.0 > Reporter: Scott Clasen > > It appears that when running in shared master slave configuration one cant > connect to the jmx console or user activemq-admin to stop the slave. > Start a slave with a master running > ACTIVEMQ_HOME: /itdept/apache-activemq-5.2.0 > ACTIVEMQ_BASE: /itdept/apache-activemq-5.2.0 > Loading message broker from: > xbean://itdept//messagebroker/activemq-config/broker3.xml > INFO BrokerService - Using Persistence Adapter: > AMQPersistenceAdapter(/datafiles/itdept//activemq-journal) > WARN AMQPersistenceAdapter - Waiting to Lock the Store > /datafiles/itdept/activemq-journal > Notice that no connections including jmx have been started...attempts to stop > the broker with activemq-admin fail with..Caused by: > java.net.ConnectException: Connection refused > Kill the master and get > INFO AMQPersistenceAdapter - Aquired lock for AMQ > Store/datafiles/itdept/activemq-journal > INFO BrokerService - ActiveMQ 5.2.0 JMS Message Broker > (messagebroker3) is starting > INFO BrokerService - For help or more information please > see: http://activemq.apache.org/ > INFO KahaStore - Kaha Store using data directory > /datafiles/itdept/activemq-journal/kr-store/data > INFO ManagementContext - JMX consoles can connect to > service:jmx:rmi:///jndi/rmi://localhost:55563/jmxrmi > INFO TransportServerThreadSupport - Listening for connections at: > tcp://0.0.0.0:55553 > INFO TransportConnector - Connector tcp Started > INFO BrokerService - ActiveMQ JMS Message Broker > (messagebroker3, ID:nymb02d-59998-1245957027403-0:0) started > INFO log - Logging to > org.slf4j.impl.JCLLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog > INFO log - jetty-6.1.9 > INFO log - web...@1288520654 at > http://0.0.0.0:55573/admin > INFO log - Started > selectchannelconnec...@0.0.0.0:55573 > Now you can connect via JMX and concole.... > brokers are very simply configured... > broker3 > <broker:broker useJmx="true" persistent="true" brokerName="messagebroker3"> > <broker:managementContext> > <broker:managementContext connectorPort="55563" > jmxDomainName="messagebroker3"/> > </broker:managementContext> > <broker:persistenceAdapter> > <broker:amqPersistenceAdapter > directory="/datafiles/itdept/activemq-journal"/> > </broker:persistenceAdapter> > <broker:transportConnectors> > <broker:transportConnector name="tcp" uri="tcp://0.0.0.0:55553"/> > </broker:transportConnectors> > </broker:broker> > broker 4 > <broker:broker useJmx="true" persistent="true" brokerName="messagebroker4"> > <broker:managementContext> > <broker:managementContext connectorPort="55564" > jmxDomainName="messagebroker4"/> > </broker:managementContext> > <broker:persistenceAdapter> > <broker:amqPersistenceAdapter > directory="/datafiles/itdept/activemq-journal"/> > </broker:persistenceAdapter> > <broker:transportConnectors> > <broker:transportConnector name="tcp" uri="tcp://0.0.0.0:55554"/> > </broker:transportConnectors> > </broker:broker> -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.