Dejan, Two thoughts:
1. Reducing the time from 30s to nil may sound like the "right thing to do" but may actually create a new problem - administrators may now see some kind of problem but delay fixing the underlying problem because the server was killed pretty quickly anyway. Indeed some less observant admins may not even spot the lack of graceful shutdown facility at all. 2. When executing "setup" wouldn't it be better to correct the resulting default script in the first place, rendering my work on investigating the cause and eventually writing that article thankfully redundant? James On 1 September 2010 13:55, Dejan Bosanac <de...@nighttale.net> wrote: > Thanks James. As promised I improved the stop logic a bit - > https://issues.apache.org/activemq/browse/AMQ-2884 > > Would be great if you could test it. > > 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 Tue, Aug 31, 2010 at 11:03 PM, James Green <james.mk.gr...@gmail.com> > wrote: >> As promised, I've documented what I did here: >> http://www.jmkg.co.uk/2010/08/31/installing-activemq-on-ubuntu/ >> >> On 29 August 2010 08:28, Romain CHANU <romainch...@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.gr...@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: >>>> jam...@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 >>>> Heap sizes: current=15872k free=15453k max=506816k >>>> JVM args: -Dactivemq.classpath=/opt/activemq/conf; >>>> -Dactivemq.home=/opt/activemq -Dactivemq.base=/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: >>>> java.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: >>>> java.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 >>>> >>> >> >
