Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of chubrilo@gmail.com designates
 209.85.160.171 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        b=N1vf+2UWNhAjhxpXoo7w5wb4NsSYN/FZsjOkuHaV8zV5PLK5ZNOyWtn2RP8Xso5f1c
         i/6iXxc6/pbRdZoVlmcMRfr8zw6JOxMzIbWimaXBWZB116GJOqek+im0Vopu/Dddmxjh
         pC0DKS57qFhytYQEzgH6ZLjk9sHcTwSammwjg=
MIME-Version: 1.0
Sender: chubrilo@gmail.com
In-Reply-To: <AANLkTi=6m7ZYBQkbKQ=2zBz72eq5Lf9J5TGc3ZKG+4Sf@mail.gmail.com>
References: <AANLkTi=a=5KOAykjWK3iB8t6rrEy6OkP_44MhxM8WCjp@mail.gmail.com>
	<AANLkTi=6m7ZYBQkbKQ=2zBz72eq5Lf9J5TGc3ZKG+4Sf@mail.gmail.com>
Date: Mon, 30 Aug 2010 10:17:05 +0200
Message-ID: <AANLkTi=i7_LQe9bA0D3tm418SctzwvdXeJK662xiLRC4@mail.gmail.com>
Subject: Re: Unix shell script to stop activemq
From: Dejan Bosanac <dejan@nighttale.net>
To: users@activemq.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,

stop command tries first to connect to the broker using JMX, and waits
for 30 sec to be stopped. Only after that it tries to kill it. Perhaps
you don't have JMX turned on or the script for some reason cannot
connect to it.

I opened a Jira issue to improve on this behavior
https://issues.apache.org/activemq/browse/AMQ-2884

In the meantime, you can try to see why the client cannot connect to
the the broker's JMX. Perhaps you should use --jmxurl option if you're
not using standard host/port
(http://activemq.apache.org/activemq-command-line-tools-reference.html#Acti=
veMQCommandLineToolsReference-shutdown)
or modify ACTIVEMQ_KILL_MAXSECONDS variable in bin/activemq script to
make this wait period shorter.


Cheers
--
Dejan Bosanac - http://twitter.com/dejanb

Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net


On Sun, Aug 29, 2010 at 9:28 AM, Romain CHANU <romainchanu@gmail.com> wrote=
:
> Hi James,
>
> I have the issue as well. Have you found anything solution yet?
>
> Cheers,
>
> Romain
>
> On 25 August 2010 00:28, James Green <james.mk.green@gmail.com> wrote:
>
>> Hi,
>>
>> Using 5.4.0 I've symlinked /etc/init.d/activemq to
>> /opt/activemq/bin/activemq and ran the setup command.
>>
>> I am able to start the process fine, but when I come to stop it I have
>> to wait thirty seconds because of this:
>> jamesg@blofeld:/opt/activemq/conf$ sudo /etc/init.d/activemq stop
>> INFO: Loading '/etc/default/activemq'
>> INFO: Using java '/usr/bin/java'
>> INFO: changing to user 'activemq' to invoke java
>> INFO: Waiting at least 30 seconds for regular process termination of
>> pid '25806' : Java Runtime: Sun Microsystems Inc. 1.6.0_18
>> /usr/lib/jvm/java-6-openjdk/jre
>> =A0Heap sizes: current=3D15872k =A0free=3D15453k =A0max=3D506816k
>> =A0 =A0JVM args: -Dactivemq.classpath=3D/opt/activemq/conf;
>> -Dactivemq.home=3D/opt/activemq -Dactivemq.base=3D/opt/activemq
>> ACTIVEMQ_HOME: /opt/activemq
>> ACTIVEMQ_BASE: /opt/activemq
>> ERROR: java.lang.RuntimeException: Failed to execute stop task.
>> Reason: java.io.IOException: Failed to retrieve RMIServer stub:
>> javax.naming.ServiceUnavailableException [Root exception is
>> java.rmi.ConnectException: Connection refused to host: 127.0.0.1;
>> nested exception is:
>> =A0 =A0 =A0 =A0java.net.ConnectException: Connection refused]
>> java.lang.RuntimeException: Failed to execute stop task. Reason:
>> java.io.IOException: Failed to retrieve RMIServer stub:
>> javax.naming.ServiceUnavailableException [Root exception is
>> java.rmi.ConnectException: Connection refused to host: 127.0.0.1;
>> nested exception is:
>> =A0 =A0 =A0 =A0java.net.ConnectException: Connection refused]
>>
>> Etc.
>>
>> I've made attempts at tweaking things according to the web
>> instructions without any changes being noticed.
>>
>> So what default settings do need changing for a Linux distribution to
>> elegantly shut down the server?
>>
>> James
>>
>