karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Resolved] (KARAF-3853) Use configured Java path to startup wrapper
Date Mon, 08 Feb 2016 16:43:39 GMT

     [ https://issues.apache.org/jira/browse/KARAF-3853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jean-Baptiste Onofré resolved KARAF-3853.
    Resolution: Fixed

> Use configured Java path to startup wrapper
> -------------------------------------------
>                 Key: KARAF-3853
>                 URL: https://issues.apache.org/jira/browse/KARAF-3853
>             Project: Karaf
>          Issue Type: Wish
>    Affects Versions: 3.0.3
>            Reporter: Christian Lutz
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 4.1.0, 3.0.6, 4.0.5
> I stumbled across the following situation. A windows Server 2012 R2 installed a JDK7
with a public JRE (http://stackoverflow.com/questions/21412853/java-windows7-system32-folder-java-exe).
> Now, I tried to install a karaf with a provided jdk 8. Starting this via the command
line worked fine. After the first start I installed the service-wrapper, so far so good. But
starting the server via the windows server brought me some trouble, because JRE 7 had been
used to startup. 
> First I didn't understand why, because in the wrapper.conf the correct path to karaf/opt/jdk
was configured. But then I found this "By default, the wrapper sets the JAVA_HOME in etc/karaf-wrapper.conf
file. However, the bin/karaf-service script uses java. If required, you have to define the
JAVA_HOME in this bin/karaf-service script." I found this sentence in section "Configuration
Hint" version 2.3 and it helped me a lot.
> So my wish is, either add this sentence to the current documentation, also. Or much better
use the configured Java path within wrapper.conf to startup the service.  

This message was sent by Atlassian JIRA

View raw message