> James Strachan wrote > > On 29 Jul 2005, at 12:08, Olaf Bergner wrote: > > > > I resorted to using Tanukisoft's Java Service Wrapper to solve this > > problem. > > Now I've ServiceMix running as Windows NT Service, which IMHO is more > > appropriate anyway. > > > > BTW it'd be nice to distribute a Java Service Wrapper binding for > ServiceMix as part of the standard distro. Olaf, do you fancy > contributing the config file stuff you created?
Sure, see the attached wrapper.conf file. No rocket science yet quite a few tedious keystrokes. Some notes: (1) I am a big fan of knowing exactly what version of a software artifact I'm dealing with. Thus the NT service name I chose includes ServiceMix' current version, i.e. 1.0 M1. A more generic solution should probably settle for something like ServiceMix, period. (2) I settled for a startup type of DEMAND_START instead of the preselected AUTO_START. The choice is up to you. (3) Min/max memory are 64/512 MB resp. I find this a reasonable default. To spare you the hassle of looking it up in the docu: (1) Copy wrapper.exe from the Java Service Wrapper distro to %SERVICEMIX_HOME%/bin. (2) Copy attached bat files to %SERVICEMIX_HOME%/bin. (3) Copy wrapper.jar and wrapper.dll from the Java Service Wrapper distro to %SERVICEMIX_HOME%/lib. (4) Copy attached wrapper.conf to %SERVICEMIX_HOME%/conf. (5) Create %SERVICEMIX_HOME%/logs. Cheers, Olaf > > James Strachan > Chief Architect > LogicBlaze, Inc. - a Simula Labs Enterprise > [EMAIL PROTECTED] > www.logicblaze.com > >
