Re: [Wrapper-user] Wrapper configuration problems

[Leif M. <le...@ta...>]

Max,
Starting with version 3.0.4, you can use the Wrapper to start and stop your
service. The Wrapper's method is much more reliable than the "net start x"
command when the service takes a long time to start or stop. And if you use
the Wrapper, you will never have problems like you just had because the only
place the service name exists is in the wrapper.conf file.

See the section on Launching the Wrapper under Windows for more details.
http://wrapper.tanukisoftware.org/doc/english/launch-win.html

Basically, you would modify the batch file like this:
---
:startup
"%_APP_HOME%\bin\Wrapper.exe" -i %_WRAPPER_CONF%
if not errorlevel 1 goto end
pause

:end
---
Becomes:
---
:startup
"%_APP_HOME%\bin\Wrapper.exe" -i %_WRAPPER_CONF%
if not errorlevel 1 goto startup2
pause

:startup2
"%_APP_HOME%\bin\Wrapper.exe" -t %_WRAPPER_CONF%
if not errorlevel 1 goto end
pause

:end
---

Glad you got it working.

Cheers,
Leif

Max Stolyarov wrote:

>Leif,
>
>  Sorry of all the confusion I caused with this e-mail thread. After careful
>testing yesterday and review of my code, I determined that was an error in
>my coding and nothing to do with the wrapper. What happened, is I modified
>the bat file that shipped with wrapper to automatically start the service
>after it is installed, but when I modified the service name in the wrapper
>Config file I forgot to update the service name in the installation bat file
>where I tried to start the service with a 'net start' command. That was the
>reason why any time I tried to start the service it would give me an error,
>service name is invalid.... Sorry again. Thanks for all of your time and
>great explanations.
>
>Max
>
>  
>