Re: [Wrapper-user] wrapper dont start

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

Rob,
Agreed.  I have added some advice messages when the Wrapper fails to
launch the JVM on Windows or UNIX platforms.   This was actually a
little difficult on UNIX because the logging needs to take place after
the Wrapper has been forked to launch the JVM.

Anyway.  This will be in the upcoming 3.3.4 release.

Cheers,
Leif

On Mon, Apr 6, 2009 at 9:08 PM, Leland, Robert <rob...@io...> wrote:
> Leif,
>
>
> In the short time I have been a member of this list I have seen similar problems of just using 'java' instead of a full path. Maybe this should be  a warning in the log files, if this isn't already.
>
> -Rob
>
> ___________________________________
> Robert Leland               INTEGRITYOne  Partners
> P: (703) 581-6522                     1900 Campus Commons Drive, Suite 150
> F: (703) 476-7405                      Reston, VA 20191
> rob...@io...
>
> BUSINESS CONSULTING | TECHNOLOGY | INNOVATION R&D
>
> ________________________________
>
> From: Leif Mortenson [mailto:lei...@ta...]
> Sent: Mon 4/6/2009 8:05 AM
> To: wra...@li...
> Subject: Re: [Wrapper-user] wrapper dont start
>
>
>
> Juergen,
> Your wrapper.java.command appears to be:
> wrapper.java.command=java
>
> Most likely java does not exist on the PATH in the environment where
> the Wrapper is being run.
>
> Try setting it to one of the following:
> wrapper.java.command=%JAVA_HOME%/bin/java
> or
> wrapper.java.command=/full/path/to/sdk/bin/java
>
> The first assumes that the JAVA_HOME environment variable is set.
>
> In the command that you sent, I notice that the M2_REPO, MULE_LIB, and
> LD_LIBRARY_PATH environment variables are also all undefined.
>
> Cheers,
> Leif
>
>
> On Mon, Apr 6, 2009 at 7:45 PM, Hans-Juergen Schumacher
> <ju...@si...> wrote:
>> Hello Leif,
>>
>> here is the output. Please let me know if you have any idea.
>>
>> Working directory set to: /home/tom_12/smscki/registration-mule/bin
>> --> Wrapper Started as Console
>> Using tick timer.
>> server listening on port 32000.
>> Classpath element, wrapper.java.classpath.2, does not exist: %MULE_LIB%
>> Command[0] : java
>> Command[1] : -Dmule.home=/home/tom_12/smscki/registration-mule
>> Command[2] : -Dmule.base=/home/tom_12/smscki/registration-mule
>> Command[3] : -Dm2.repo="%M2_REPO%"
>> Command[4] :
>> -Dmule.bootstrap.library.download.description.1=javax.activation.DataSource,/javax/activation/activation/1.1,activation-1.1.jar
>> Command[5] :
>> -Dmule.bootstrap.library.download.description.2=javax.mail.Message,/javax/mail/mail/1.4,mail-1.4.jar
>> Command[6] :
>> -Djava.endorsed.dirs=/home/tom_12/smscki/registration-mule/lib/endorsed
>> Command[7] : -Xmx512m
>> Command[8] :
>> -Djava.library.path=%LD_LIBRARY_PATH%:/home/tom_12/smscki/registration-mule/lib/boot
>> Command[9] : -classpath
>> Command[10] :
>> /home/tom_12/smscki/registration-mule/bin/../conf:%MULE_LIB%:/home/tom_12/smscki/registration-mule/lib/boot/wrapper-3.2.3.jar:/home/tom_12/smscki/registration-mule/lib/boot/mule-module-boot-1.4.4.jar:/home/tom_12/smscki/registration-mule/lib/boot/commons-cli-1.0.jar
>> Command[11] : -Dwrapper.key=iXleguo6tkdqhlTT
>> Command[12] : -Dwrapper.port=32000
>> Command[13] : -Dwrapper.jvm.port.min=31000
>> Command[14] : -Dwrapper.jvm.port.max=31999
>> Command[15] : -Dwrapper.debug=TRUE
>> Command[16] : -Dwrapper.pid=28454
>> Command[17] : -Dwrapper.version=3.2.3
>> Command[18] : -Dwrapper.native_library=wrapper
>> Command[19] : -Dwrapper.cpu.timeout=10
>> Command[20] : -Dwrapper.jvmid=1
>> Command[21] : org.mule.modules.boot.MuleBootstrap
>> Command[22] : console0
>> Launching a JVM...
>> Signal trapped.  Details:
>>   signal number=17 (SIGCHLD), source="unknown"
>> Received SIGCHLD, checking JVM process status.
>> JVM process exited with a code of 1, setting the wrapper exit code to 1.
>> JVM exited while loading the application.
>> Unable to start JVM: No such file or directory (2)
>> JVM was only running for 0 seconds leading to a failed restart count of 1.
>> Waiting 5 seconds before launching another JVM.
>>
>>
>> Thx a lot,
>>
>> juergen
>>
>> Leif Mortenson wrote:
>>
>> Juergen,
>> Try setting the wrapper.java.command.loglevel=INFO property.  This
>> will cause the Wrapper to log the full java command line.   Most
>> likely java binary is not being found correctly.
>>
>> If that does not make the problem obvious.  Please set the
>> wrapper.debug=TRUE property and reply with the resulting wrapper.log
>> file attached.  I should be able to point out the problem for you
>> then.
>>
>> Cheers,
>> Leif
>>
>> On Sat, Apr 4, 2009 at 1:01 AM, Hans-Juergen Schumacher
>> <ju...@si...> wrote:
>>
>>
>> Hi,
>> I always get a failure when I try to start the wrapper:
>>
>> wrapper  | Unable to start JVM: No such file or directory
>>
>> I have no idea what file or directory he is looking for. I think
>> something with permissions maybe...any help is appreciated.
>>
>> Thx
>> juergen