After some more reading, it seems Method 2 is better: http://wrapper.tanukisoftware.org/doc/english/integrate-start-stop-win.html
These sections change: # Java Main class. This class must implement the WrapperListener interface # or guarantee that the WrapperManager class is initialized. Helper # classes are provided to do this for you. See the Integration section # of the documentation for details. wrapper.java.mainclass=org.tanukisoftware.wrapper.WrapperStartStopApp ... # Application parameters. Add parameters as needed starting from 1 wrapper.app.parameter.1=org.apache.activemq.console.Main wrapper.app.parameter.2=2 wrapper.app.parameter.3=start wrapper.app.parameter.4=xbean:activemq.xml wrapper.app.parameter.5=org.apache.activemq.console.Main wrapper.app.parameter.6=true wrapper.app.parameter.7=1 wrapper.app.parameter.8=stop wrapper.app.parameter.6=true tells JSW to wait for all threads to terminate. Presumably ActiveMQ shuts down cleanly, so this shouldn't be a problem. > -----Original Message----- > From: Albert Strasheim [mailto:[EMAIL PROTECTED] > Sent: 18 September 2006 17:31 > To: [email protected] > Subject: ActiveMQ as a Windows Service > > <snip>
