You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jamie goodyear (Assigned) (JIRA)" <ji...@apache.org> on 2011/10/28 16:34:32 UTC
[jira] [Assigned] (KARAF-972) KARAF_OPTS is not propagated to start
command in admin script
[ https://issues.apache.org/jira/browse/KARAF-972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jamie goodyear reassigned KARAF-972:
------------------------------------
Assignee: Jamie goodyear
> KARAF_OPTS is not propagated to start command in admin script
> -------------------------------------------------------------
>
> Key: KARAF-972
> URL: https://issues.apache.org/jira/browse/KARAF-972
> Project: Karaf
> Issue Type: Improvement
> Affects Versions: 2.1.6, 2.2.4
> Reporter: Jonathan Anstey
> Assignee: Jamie goodyear
> Attachments: propagateKarafOpts-2.1.x.patch, propagateKarafOpts-2.2.x.patch, propagateKarafOpts-trunk.patch
>
>
> You can use KARAF_OPTS to set extra properties for your Karaf process when using bin/karaf. However, even though KARAF_OPTS is defined and used in bin/admin, the extra properties do not make it to the start command. The start command creates a new process so Karaf needs to propagate the KARAF_OPTS values to this new process. Attaching patches shortly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira