You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2016/05/27 15:38:13 UTC

[jira] [Updated] (CASSANDRA-11888) cassandra-env.sh may not work properly with jvm args containing a space

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

Sylvain Lebresne updated CASSANDRA-11888:
-----------------------------------------
    Labels: lhf  (was: )

> cassandra-env.sh may not work properly with jvm args containing a space
> -----------------------------------------------------------------------
>
>                 Key: CASSANDRA-11888
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11888
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: linux
>            Reporter: Russ Hatch
>            Priority: Minor
>              Labels: lhf
>
> When using the JVM_EXTRA_OPTS environment variable, it looks like there's some cases that may not work if an env var contains a space.
> For example, setting:
> {noformat}
> export JVM_EXTRA_OPTS='-XX:OnOutOfMemoryError="echo oh_no"'
> {noformat}
> Results in the jvm not starting because the resultant startup command looks to java like it should load a class called oh_no.
> {noformat}
> Error: Could not find or load main class oh_no
> {noformat}
> I think this results from the last line of cassandra-env.sh, where it does this:
> {noformat}
> JVM_OPTS="$JVM_OPTS $JVM_EXTRA_OPTS"
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)