cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-7572) cassandra-env.sh fails to find Java version if JAVA_TOOL_OPTIONS in environment
Date Mon, 04 Aug 2014 08:32:12 GMT

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

Sylvain Lebresne updated CASSANDRA-7572:
----------------------------------------

    Fix Version/s:     (was: 2.1.0)
                   2.1 rc5

> cassandra-env.sh fails to find Java version if JAVA_TOOL_OPTIONS in environment
> -------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-7572
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7572
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Config
>         Environment: Linux/darwin/etc
>            Reporter: Gregory Ramsperger
>            Assignee: Gregory Ramsperger
>             Fix For: 2.0.10, 2.1 rc5
>
>
> Parsing of Java version is done in cassandra-env.sh via
> {code}
> java_ver_output=`"${JAVA:-java}" -version 2>&1`
> jvmver=`echo "$java_ver_output" | awk -F'"' 'NR==1 {print $2}'`
> {code}
> This fails if the first line of output from `java -version` does not contain the version.
When JAVA_TOOL_OPTIONS is set as the output is
> {quote}
> Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8
> java version "1.7.0_40"
> Java(TM) SE Runtime Environment (build 1.7.0_40-b43)
> Java HotSpot(TM) 64-Bit Server VM (build 24.0-b56, mixed mode)
> {quote}
> Parsing this is not guaranteed to work as there is no contract for this output. The recommended
way of dealing with this is via a Java application (which will have access to each of these
pieces).
> If you want to keep with this model of doing things, you can apply a very small but hacky
patch:
> {code}
> -jvmver=`echo "$java_ver_output" | awk -F'"' 'NR==1 {print $2}'`
> +jvmver=`echo "$java_ver_output" | grep 'java version' | awk -F'"' 'NR==1 {print $2}'`
>  JVM_VERSION=${jvmver%_*}
>  JVM_PATCH_VERSION=${jvmver#*_}
> @@ -100,7 +100,7 @@
>  fi
> -jvm=`echo "$java_ver_output" | awk 'NR==2 {print $1}'`
> +jvm=`echo "$java_ver_output" | grep -A 1 'java version' | awk 'NR==2 {print $1}'`
>  case "$jvm" in
>      OpenJDK)
> {code}
> Otherwise, you need to write a java app, compiled for older versions, that returns this
data via the java.specification.version and a combination of java.vm.name and java.vm.vendor.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message