You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Eric Evans (JIRA)" <ji...@apache.org> on 2013/09/30 17:08:27 UTC
[jira] [Resolved] (CASSANDRA-4638) Patch to bin/cassandra to use
64bit JVM if available
[ https://issues.apache.org/jira/browse/CASSANDRA-4638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Evans resolved CASSANDRA-4638.
-----------------------------------
Resolution: Fixed
committed; thanks for the report
> Patch to bin/cassandra to use 64bit JVM if available
> ----------------------------------------------------
>
> Key: CASSANDRA-4638
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4638
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.1.4
> Environment: Tested on Solaris 11 with Oracle supplied JVM 1.6 and 1.7
> Reporter: Bernhard Roth
> Labels: 64bit, linux, solaris
> Attachments: 4638.patch, cassandra.patch
>
> Original Estimate: 0.25h
> Remaining Estimate: 0.25h
>
> Cassandra uses by default the JAVA binary at $JAVA_HOME/bin and complains at start that the 64bit version should be used.
> Well, even if the 64bit JAVA version is installed, cassandra still does not use it.
> Attached patch solves this problem by checking if $JAVA_HOME/bin/amd64/java binary exists. If yes, it will be used for cassandra.
--
This message was sent by Atlassian JIRA
(v6.1#6144)