Re: [Wrapper-user] does wrapper depend on JAVA_HOME?

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

Try running the Wrapper with wrapper.debug=true set in your wrapper.conf
file. This will cause the full command used to launch java to be logged.
This should hep you to narrow down the problem.

If you see something like %JAVA_HOME%, unexpanded in the generated
command, than means that the environment variable is not being registered
correctly.

What Wrapper version are you using. 3.1.0 handles spaces around the '='
in property declarations correctly, but the properties are not recognized in
earlier versions if the spaces are there.


Cheers,
Leif

Cocalea, Eugen wrote:

>Hi,
>
>Unfortunately, it seems that (in my case), set.JAVA_HOME=<path_to_java_home>
>doesn't work. I don't know why.
>
>I tried both setting it in wrapper.conf and supplying it in the command
>line, like:
>
>wrapper -c wrapper.conf "set.JAVA_HOME=<path_to_java_home>"
>
>In both cases, with
>
>wrapper.java.command = %JAVA_HOME%/bin/java
>
>the wrapper complains that it cannot execute the command.
>
>/EC
>
>-----Original Message-----
>From: Leif Mortenson [mailto:le...@ta...] 
>Sent: Wednesday, May 26, 2004 10:11 AM
>To: wra...@li...
>Subject: Re: [Wrapper-user] does wrapper depend on JAVA_HOME?
>
>Eugen,
>The Wrapper does not do anything with the JAVA_HOME environment
>variable. As long as you are not referencing it in your wrapper.conf file
>then there is also no way for the application running the JVM to reference
>it.
>JAVA_HOME is usually passed to the JVM using a system property like:
>
>-Djavahome=%JAVA_HOME%
>
>It is perfectly safe to do the following:
>wrapper.java.command=../jre/bin/java
>
>One option is to define the JAVA_HOME environment variable within
>your wrapper.conf file as follows:
>
>set.JAVA_HOME=../jre
>wrapper.java.command=%JAVA_HOME%/bin/java
>
>This has the benefit of making it easy to reference the JRE location
>throughout your wrapper.conf file. The user can also use a system
>value by simply commenting out the set line.
>
>Cheers,
>Leif
>
>
>
>Cocalea, Eugen wrote:
>
>  
>
>>Hello,
>>
>>This is a bit tricky, because not even me know what the question is about.
>>
>>I have a java application that I want to run as a windows service and
>>I use wrapper to do this.
>>
>>My app wrapper.conf used to have
>>
>>wrapper.java.command=%JAVA_HOME%/bin/java
>>
>>The problem is that I have to run different versions of the
>>application, that are certified against different JREs.
>>
>>So, my question is: if I hardcode the path to the JRE I need in
>>wrapper.java.command, do I need to check anything else to see if the
>>application really uses that JRE?
>>
>>Example:
>>
>>- JAVA_HOME points to JRE 1.3
>>
>>- I need to run the app with JRE 1.4
>>
>>- wrapper.java.command is <JRE1.4_install_path>/bin/java
>>
>>I should be safe, correct? *_Assuming my application doesn't use
>>JAVA_HOME._*
>>
>>    
>>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: Oracle 10g
>Get certified on the hottest thing ever to hit the market... Oracle 10g. 
>Take an Oracle 10g class now, and we'll give you the exam FREE.
>http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
>_______________________________________________
>Wrapper-user mailing list
>Wra...@li...
>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: Oracle 10g
>Get certified on the hottest thing ever to hit the market... Oracle 10g. 
>Take an Oracle 10g class now, and we'll give you the exam FREE.
>http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
>_______________________________________________
>Wrapper-user mailing list
>Wra...@li...
>https://lists.sourceforge.net/lists/listinfo/wrapper-user
>
>  
>