Re: [Wrapper-user] Win 2000 Service problem

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

Stefan,
    If your application is working as a console application, but failing 
when run as a service,
your problem is most likely related to a permissions issue or a 
difference in the environment
variables that are available.

    In any case, the first thing you should do when debugging any 
Wrapper problem is to
look in the wrapper.log file.   If nothing is obvious, try adding the 
following property to your
wrapper.conf and then rerunning your application.
    wrapper.debug=true

    This will cause the wrapper to dump, amongst other things, the full 
java command line
used to actually launch Java.  Compare the command line used to launch 
the application
as a service versus the one used to launch in console mode.

    The most common problem here is setting an environment variable in 
the batch file
used to install and then run as a service.  Environment variables set in 
the batch file
will not be available when run as a service.  To do this, you need to 
add them to the
command line used to install the Wrapper as a service.  As follows:

Wrapper.exe -i ..\conf\wrapper.conf set.MY_ENV=testval

    You can also define environment variables within the wrapper.conf 
using the same
syntax.

    Post back whether or not you get things working.   If you are still 
having problems,
then attach your wrapper.conf and the wrapper.log output from a SINGLE 
run with
debug output enabled.

Cheers,
Leif