Hi, > 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. >
Can you test the latest snapshot which should include the improvement of the stop routine. https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/apache-activemq/5.5-SNAPSHOT/ But anyways, you can always use some reasonable value like 5-10 sec. > 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? All contributions and improvements are welcomed. 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
