Re: [Wrapper-user] Win 2000 Service problem

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

Stefan,
    You sent me lots of info, but skipped the one key piece that I need 
to respond, the
log output of the run when you attempt to start the application as a 
service.  Also.  When
sending in log files, please do not trim them down.  I know the idea is 
to reduce the size of
the emails, but you removed a lot of the information that I wanted to 
see. :-)

>If the InstallApp-NT.bat cannot use standard batch file commands for setting
>up Env variables - Can you correct the example bat files 
>  
>
The environment variables declared in the scripts are only really meant 
to be used
from within the batch files, not for references in the wrapper.conf 
file.  So they are
correct in that sense.

Looking at your wrapper.conf file, I have one idea for what the problem 
may be.
(It would be answered quickly by seeing the debug log output when you 
attempt to
launch the Wrapper as a service.)

You have a few references to the WRAPPERDIR environment variable in your 
conf
file.  If you have not set this as a system level environment variable 
or specified it on
the command line when the wrapper was installed as a service this will 
not work:
wrapper.exe -i ../conf/wrapper.conf set.WRAPPERDIR=C:\MyApp

>wrapper.java.classpath.2=%WRAPPERDIR%/lib/wrapper.jar
>
>wrapper.java.library.path.1=%WRAPPERDIR%/lib
>  
>
You might want to consider just using a relative path as follows:
wrapper.java.classpath.2=../lib/wrapper.jar
wrapper.java.library.path.1=../lib

Same goes for the following log location.  If that file can not be 
accessed for any
reason then the wrapper will open a file called wrapper.log in the 
windows system
directory.   That may be why you have not found the file this far.

>wrapper.logfile=%WKDIR%logs/HRScannerService.log
>  
>
This could also be
wrapper.logfile=../logs/HRScannerService.log

Cheers,
Leif