karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (Commented) (JIRA) <j...@apache.org>
Subject [jira] [Commented] (KARAF-1241) admin script does not pass on JAVA_OPTS to instance
Date Wed, 29 Feb 2012 10:07:57 GMT

    [ https://issues.apache.org/jira/browse/KARAF-1241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13219056#comment-13219056
] 

Jean-Baptiste Onofré commented on KARAF-1241:
---------------------------------------------

I don't think it's a good idea. The child instances are isolated from the master one, or from
the system properties.

To pass the memory setup, you have to use admin:change-opts.

For instance:

karaf@root> admin:create test
karaf@root> admin:change-opts test "-Xmx1024"

bin/admin start test
[org.apache.karaf.admin.internal.InstanceImpl] : Starting instance test with command: /opt/jdk/1.6.0_26/jre/bin/java
-Xmx1024m  -Djava.util.logging.config.file="/home/jbonofre/apach......

So it looks good to me.

The args passed via the admin script are ignored, and it's what we expect.
                
> admin script does not pass on JAVA_OPTS to instance
> ---------------------------------------------------
>
>                 Key: KARAF-1241
>                 URL: https://issues.apache.org/jira/browse/KARAF-1241
>             Project: Karaf
>          Issue Type: Bug
>    Affects Versions: 2.2.5
>         Environment: apache-karaf-2.2.5.tar.gz
>            Reporter: Jonathan Anstey
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 2.2.6, 3.0.0
>
>         Attachments: KARAF-1241.patch
>
>
> The JAVA_OPTS set in the bin/admin script are passed on to the admin process but then
when the admin process kicks off a new Karaf instance, the options get lost. For example,
when setting the max JVM memory to 1024M as follows:
> {code}
> [janstey@duffman apache-karaf-2.2.5]$ export JAVA_MAX_MEM=1024M
> {code}
> You can see that the default of 512M is still used for the Karaf instance:
> {code}
> [janstey@duffman apache-karaf-2.2.5]$ ./bin/admin start root
> [org.apache.karaf.admin.internal.InstanceImpl] : Starting instance root with command:
/opt/jdk1.6.0_23/jre/bin/java -server -Xmx512M -Dcom.sun.management.jmxremote  -Djava.util.logging.config.file="/opt/fuse/apache-karaf-2.2.5/etc/java.util.logging.properties"
-Djava.endorsed.dirs="/opt/jdk1.6.0_23/jre/jre/lib/endorsed:/opt/jdk1.6.0_23/jre/lib/endorsed:/opt/fuse/apache-karaf-2.2.5/lib/endorsed"
-Djava.ext.dirs="/opt/jdk1.6.0_23/jre/jre/lib/ext:/opt/jdk1.6.0_23/jre/lib/ext:/opt/fuse/apache-karaf-2.2.5/lib/ext"
-Dkaraf.home="/opt/fuse/apache-karaf-2.2.5" -Dkaraf.base="/opt/fuse/apache-karaf-2.2.5" -Dkaraf.startLocalConsole=false
-Dkaraf.startRemoteShell=true -classpath /opt/fuse/apache-karaf-2.2.5/lib/karaf.jar:/opt/fuse/apache-karaf-2.2.5/lib/karaf-jaas-boot.jar
org.apache.karaf.main.Main
> {code}
> Attaching a fix 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

       

Mime
View raw message