From dev-return-17502-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org Fri Nov 06 08:53:24 2009 Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 28902 invoked from network); 6 Nov 2009 08:53:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 6 Nov 2009 08:53:24 -0000 Received: (qmail 9480 invoked by uid 500); 6 Nov 2009 08:53:23 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 9462 invoked by uid 500); 6 Nov 2009 08:53:22 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 9452 invoked by uid 99); 6 Nov 2009 08:53:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Nov 2009 08:53:22 +0000 X-ASF-Spam-Status: No, hits=-1998.5 required=10.0 tests=ALL_TRUSTED,NORMAL_HTTP_TO_IP,WEIRD_PORT X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Nov 2009 08:53:15 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id C7106234C1EE for ; Fri, 6 Nov 2009 00:52:53 -0800 (PST) Message-ID: <77490795.1257497573809.JavaMail.jira@brutus> Date: Fri, 6 Nov 2009 00:52:53 -0800 (PST) From: "Dejan Bosanac (JIRA)" To: dev@activemq.apache.org Subject: [jira] Assigned: (AMQ-2306) Unable to monitor or manage slave brokers in shared filesystem master slave configuration In-Reply-To: <558863807.1245956979360.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: ae95407df07c98740808b2ef9da0087c X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/activemq/browse/AMQ-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac reassigned AMQ-2306: ---------------------------------- Assignee: Dejan Bosanac > 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 > Assignee: Dejan Bosanac > > It appears that when running in shared master slave configuration one cant connect to the jmx console or use 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 - WebApp@1288520654 at http://0.0.0.0:55573/admin > INFO log - Started SelectChannelConnector@0.0.0.0:55573 > Now you can connect via JMX and concole.... > brokers are very simply configured... > broker3 > > > > > > > > > > > > broker 4 > > > > > > > > > > > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.