cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (CASSANDRA-2785) should export JAVA variable in the bin/cassandra and use that in the cassandra-env.sh when check for the java version
Date Fri, 17 Jun 2011 06:08:47 GMT

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

Jonathan Ellis reassigned CASSANDRA-2785:
-----------------------------------------

    Assignee: paul cannon

> should export JAVA variable in the bin/cassandra and use that in the cassandra-env.sh
when check for the java version
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-2785
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2785
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jackson Chung
>            Assignee: paul cannon
>
> I forgot which jira we add this java -version check in the cassandra-env.sh (for adding
jamm to the javaagent), but we should probably use the variable JAVA set in bin/cassandra
(will need export) and use $JAVA instead of "java" in the cassandra-env.sh
> In a situation where JAVA_HOME may have been properly set as the Sun's java but the PATH
still have the OpenJDK's java in front, the check will fail to add the jamm.jar, even though
the cassandra jvm is properly started via the Sun's java.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message