cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Evans (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6240) CLASSPATH logic from init script is unused, JNA isn't loaded
Date Fri, 25 Oct 2013 20:19:32 GMT


Eric Evans commented on CASSANDRA-6240:

This was fixed in the 2.0 branch as part of CASSANDRA-6101, and will be released as part of

There is one remaining issue with the init script that has gotten hung in review.  [~paravoid]
if you could have a look at CASSANDRA-6131 and comment on it there, I'd be very grateful (I'll
buy you a cheesesteak sandwich in Portland next summer :)).

> CLASSPATH logic from init script is unused, JNA isn't loaded
> ------------------------------------------------------------
>                 Key: CASSANDRA-6240
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Packaging
>            Reporter: Faidon Liambotis
>            Assignee: Eric Evans
> The init script has a classpath() function that collects all the jars and even includes
this piece of code to work with the standard Debian/Ubuntu libjna-jar:
> {code:none}
>     # use JNA if installed in standard location
>     [ -r /usr/share/java/jna.jar ] && cp="$cp:/usr/share/java/jna.jar"
> {code}
> This seems very nice and correct, however the classpath() function is never called and
is entirely unused :) Instead, /usr/bin/cassandra is called, which in turn includes /usr/share/cassandra/,
which has basically similar code to collect the jars for CLASSPATH but a) without the JNA
standard path trick b) without using EXTRA_CLASSPATH (from /etc/default/cassandra) at all,
so Cassandra boots without either JNA nor EXTRA_CLASSPATH, contrary to expectations.
> There are various suggestions on the web to do "ln -s /usr/share/java/jna.jar /usr/share/cassandra/lib/";
I suspect this bug to be the reason for that.
>  /usr/share/cassandra/ seems smart enough to append but not overwrite
CLASSPATH, so fixing the init script's classpath() to only include JNA + EXTRA_CLASSPATH (and
making sure it's actually getting called :)) should be enough for a fix.

This message was sent by Atlassian JIRA

View raw message