cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "paul cannon (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2647) Cassandra can't find jamm on startup
Date Mon, 16 May 2011 17:31:47 GMT


paul cannon commented on CASSANDRA-2647:

Tested and verified Eric's patch, both via initscript and invocation through /usr/sbin/cassandra;
the right path to jamm (and all the other lib jars) gets set correctly. +1 for the patch.

I think ideally the rest of the initscript would also make use of $CASSANDRA_HOME (like when
specifying the location of the jars to add to the classpath), but since the deb isn't expected
to support a change to $CASSANDRA_HOME, it's fine as is.

> Cassandra can't find jamm on startup
> ------------------------------------
>                 Key: CASSANDRA-2647
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Packaging
>    Affects Versions: 0.8 beta 1
>         Environment: Ubuntu 10.04 Lucid
>            Reporter: Marcus Bointon
>            Assignee: paul cannon
>            Priority: Minor
>             Fix For: 0.8.1
>         Attachments: v1-0001-CASSANDRA-2647-move-jars-under-lib-to-satisfy-hard-cod.txt
> I installed the Debian package (from unstable)
of Cassandra 0.8beta2 on Ubuntu 10.04 with the sun jdk over a working copy of 0.7.2. It broke
on restart.
> On startup it gives this:
> {code}
> Error occurred during initialization of VM
> agent library failed to init: instrument
> Error opening zip file or JAR manifest missing : /lib/jamm-0.2.2.jar
> {code}
> /etc/cassandra/ contains this:
> {code}
> # add the jamm javaagent
> check_openjdk=$(java -version 2>&1 | awk '{if (NR == 2) {print $1}}')
> if [ "$check_openjdk" != "OpenJDK" ]
> then
>     JVM_OPTS="$JVM_OPTS -javaagent:$CASSANDRA_HOME/lib/jamm-0.2.2.jar"
> fi
> {code}
> By default, CASSANDRA_HOME is not set, so it's looking in /lib for this jar. It seems
CASSANDRA_HOME should be set to /usr/share/cassandra, since that's where jamm-0.2.2.jar is
installed, but that means the path is still wrong.
> I set CASSANDRA_HOME to /usr/share/cassandra and changed the JVM_OPTS line to this:
> {code}
>     JVM_OPTS="$JVM_OPTS -javaagent:$CASSANDRA_HOME/jamm-0.2.2.jar"
> {code}
> and then cassandra started ok.
> Is this a bug or did I miss something?
> I also noticed that this line appears to be the only use of CASSANDRA_HOME.

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message