[CASSANDRA-11716] cassandra 2.2 fails to start on jdk7u101

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Duplicate

Environment

ubuntu 12.04 fully updated

• Severity: Normal
• Assignee: Unassigned
• Reporter: Tiago Batista
• Created: 05/May/16 06:55
• Updated: 16/Apr/19 09:30
• Resolved: 05/May/16 07:29

Description

Today I updated one of my clusters to 2.2.6, and was greeted with the message complaining about the jdk version:

$ nodetool status
Cassandra 2.0 and later require Java 7u25 or later.

After digging into it, on cassandra-env.sh, i found that you are comparing the patch levels as strings, meaning that "101" is before "25":

if [ "$JVM_VERSION" \< "1.8" ] && [ "$JVM_PATCH_VERSION" \< "25" ] ; then
    echo "Cassandra 2.0 and later require Java 7u25 or later."
    exit 1;
fi

I patched this on my system to

if [ "$JVM_VERSION" \< "1.8" ] && [ "$JVM_PATCH_VERSION" -lt "25" ] ; then
    echo "Cassandra 2.0 and later require Java 7u25 or later."
    exit 1;
fi

this seems to work on bash. I can now start cassandra successfully on that cluster.

Issue Links

• duplicates: CASSANDRA-11661 Cassandra 2.0 and later require Java 7u25 or later - jdk 101