You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2012/11/19 20:37:57 UTC
[jira] [Commented] (KARAF-2017) Service wrapper should use and
populate JAVA_HOME in conf file
[ https://issues.apache.org/jira/browse/KARAF-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500545#comment-13500545 ]
Jean-Baptiste Onofré commented on KARAF-2017:
---------------------------------------------
Fixed on karaf-2.2.x: http://svn.apache.org/viewvc?view=revision&revision=1411364
> Service wrapper should use and populate JAVA_HOME in conf file
> --------------------------------------------------------------
>
> Key: KARAF-2017
> URL: https://issues.apache.org/jira/browse/KARAF-2017
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-os-integration
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Fix For: 2.2.10, 2.3.1, 3.0.0.RC1, 3.0.0
>
>
> Now, when installing the service wrapper, it doesn't define the JAVA_HOME (defined in System properties) in etc/karaf-wrapper.conf.
> If the problem doesn't have JAVA_HOME defined at startup (in runlevel), we may encounter issue like security exception (around key negotiation).
> As the JAVA_HOME is known during the installation of the service wrapper, it makes sense to use it in etc/karaf-wrapper.conf like:
> set.default.JAVA_HOME=/java/path
> set.default.KARAF_HOME=/foobar
> set.default.KARAF_BASE=/foobar
> set.default.KARAF_DATA=/foobar/data
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira