Return-Path: 
 <dev-return-41397-apmail-activemq-dev-archive=activemq.apache.org@activemq.apache.org>
X-Original-To: apmail-activemq-dev-archive@www.apache.org
Delivered-To: apmail-activemq-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id BA1CF10267
	for <apmail-activemq-dev-archive@www.apache.org>;
 Wed, 30 Oct 2013 14:45:19 +0000 (UTC)
Received: (qmail 51729 invoked by uid 500); 30 Oct 2013 14:37:40 -0000
Delivered-To: apmail-activemq-dev-archive@activemq.apache.org
Received: (qmail 51540 invoked by uid 500); 30 Oct 2013 14:37:33 -0000
Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@activemq.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@activemq.apache.org>
List-Post: <mailto:dev@activemq.apache.org>
List-Id: <dev.activemq.apache.org>
Reply-To: dev@activemq.apache.org
Delivered-To: mailing list dev@activemq.apache.org
Received: (qmail 51477 invoked by uid 99); 30 Oct 2013 14:37:27 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Oct 2013 14:37:27 +0000
Date: Wed, 30 Oct 2013 14:37:27 +0000 (UTC)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12493021.1292112836028.5494.1383143847178@arcas>
In-Reply-To: <JIRA.12493021.1292112836028@arcas>
References: <JIRA.12493021.1292112836028@arcas>
Subject: [jira] [Updated] (AMQ-3082) Broker doesn't stop using the activemq
 script if the JMX port is changed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/AMQ-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated AMQ-3082:
-----------------------------

    Fix Version/s: 5.10.0

> Broker doesn't stop using the activemq script if the JMX port is changed
> ------------------------------------------------------------------------
>
>                 Key: AMQ-3082
>                 URL: https://issues.apache.org/jira/browse/AMQ-3082
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.4.1
>         Environment: CentOS 5.4 64 bits
>            Reporter: Iker Jimenez
>            Assignee: Claus Ibsen
>             Fix For: 5.10.0
>
>
> I have two activemq instances on the same machine. One running on all the default port settings and the other one on the following ports:
> Changed to the second activemq instance:
> in bin/activemq:
> ACTIVEMQ_SUNJMX_CONTROL="--jmxurl service:jmx:rmi:///jndi/rmi://localhost:1100/jmxrmi"
> in conf/activemq.xml
> <managementContext createConnector="true" connectorPort="1100" jmxDomainName="broker2"/>
> ...
> <transportConnector name="openwire" uri="tcp://0.0.0.0:61617"/>
> in conf/jetty.xml
> <property name="port" value="8162" />
> So when I execute bin/activemq start:
> ...
>  INFO | JMX consoles can connect to service:jmx:rmi:///jndi/rmi://localhost:1100/jmxrmi
>  INFO | Listening for connections at: tcp://myhostname:61617
> ...
> When I try to stop it, bin/activemq stop:
> ...
> INFO: There are no brokers to stop.
> .
> INFO: Regular shutdown not successful,  sending SIGKILL to process with pid '26137'
> I added some logging to the script to discover that it was doing this call:
> /usr/bin/java -Dactivemq.classpath="/home/myuser/activeMQ2/apache-activemq-5.4.1/conf;" -Dactivemq.home="/home/myuser/activeMQ2/apache-activemq-5.4.1" -Dactivemq.base="/home/myuser/activeMQ2/apache-activemq-5.4.1" -jar "/home/myuser/activeMQ2/apache-activemq-5.4.1/bin/run.jar" stop --jmxurl service:jmx:rmi:///jndi/rmi://localhost:1100/jmxrmi
> This doesn't seem to find the JMX service in the specified location, even though it is the URL that was printed at start up (See log above).
> All I wanted to have is two instances running on the same box to test a cluster configuration, but starting/stopping them correctly with the scripts seem to be a pain. A simple kill to the process PID works much better.



--
This message was sent by Atlassian JIRA
(v6.1#6144)