Re: [Wrapper-user] Error: Unable to start JVM: No such file or directory

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

Nathanael,
The cause of this problem will be obvious if you set the following property:
wrapper.java.command.loglevel=INFO

This error is stating that the Java executable could not be found.   It is
most likely a problem with your environment.  What is the value of
wrapper.java.command?

If this:
wrapper.java.command=java
then:
Your PATH environment variable does not include the location of java.

If this:
wrapper.java.command=%JAVA_HOME%/bin/java
then:
Your JAVA_HOME environment variable is not defined.

This happens because when you register any script to run on startup, it uses
the default root environment to run the service.  That environment usually
has a very simple base environment defined.  You need to make sure that any
of your environment variables are defined correctly for that environment.

Cheers,
Leif

On Wed, Jan 28, 2009 at 3:32 AM, Nathanael Costa <nca...@gm...>wrote:

> Hi,
>
> I have a java project using System Tray (The same app in thread "Unable to
> locate the class"). I set up the Wrapper on system startup (i'm using
> debian), but, when the system initialize, the wrapper doesn't start my
> service. Wrapper.log has:
>
> Launching a JVM...
> Unable to start JVM: No such file or directory (2)
> JVM process is gone.
> ^[]0;Testing^G
> <-- Wrapper Stopped
>
> Maybe the reason could be the same that Leif wrote on the other thread: X's
> libraries not available on startup.
> Can someone confirm that?
>
>