Re: [Wrapper-user] Wrapper as Linux daemon

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

Yuval,
    Try enabling debug output using the wrapper.debug=true property.  
This will show
you the full command that the Wrapper is using to launch the JVM.   The 
message you
are getting is because the command that is generated does not point to a 
valid Java
executable.  Most likely this is a PATH or environment variable 
problem.  At system
startup, not all environment variables are always setup.  The problem 
should be
obvious by looking at the debug output.

    Good news is that if you are seeing the message you posted then you 
are very
close to getting things working.

Cheers,
Leif

Yuval Zantkeren wrote:

>Hi,
>
>I did what you wrote in your replay and I got error, this is the error from
>the log file:
>
>STATUS | wrapper  | 2004/03/22 16:05:52 | Launching a JVM...
>ERROR  | wrapper  | 2004/03/22 16:05:52 | Unable to start JVM: No such file
>or directory (2)
>ERROR  | wrapper  | 2004/03/22 16:05:52 | Critical error: wait for JVM
>process failed (No child processes)
>
>Please Advise,
>
>Regards,
>
>Yuval
>  
>