[KARAF-1241] admin script does not pass on JAVA_OPTS to instance

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 2.2.5
• Fix Version/s: 2.2.6, 3.0.0

Environment

apache-karaf-2.2.5.tar.gz

• Assignee: Jean-Baptiste Onofré
• Reporter: Jonathan Anstey
• Created: 28/Feb/12 20:25
• Updated: 27/Apr/12 23:03
• Resolved: 29/Feb/12 10:07

Description

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:

[janstey@duffman apache-karaf-2.2.5]$ export JAVA_MAX_MEM=1024M

You can see that the default of 512M is still used for the Karaf instance:

[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

Attaching a fix shortly.