Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of eczech52@gmail.com designates
 209.85.210.172 as permitted sender)
MIME-Version: 1.0
Sender: eczech52@gmail.com
From: Eric Czech <eric@nextbigsound.com>
Date: Wed, 31 Aug 2011 22:38:02 -0600
Message-ID: 
 <CACjoVs+wHxWiHMZyjbkXJu4WornRATWqS=c4ySUhGNKdUa_-Ow@mail.gmail.com>
Subject: Unable to link C library (for jna.jar) on 0.7.5
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=20cf307f3ac4fd077c04abd9e4d1

--20cf307f3ac4fd077c04abd9e4d1
Content-Type: text/plain; charset=ISO-8859-1

Hi everybody,

I'm running cassandra 0.7.5 on about 20 RHEL 5 (24 GB RAM) machines and I'm
having issues with snapshots, json sstable conversions, and various nodetool
commands due to memory errors and the lack of the native access C libraries.
 I tried putting jna.jar on the classpath but I'm still seeing warnings in
the log files like "CLibrary.java (line 65) Unable to link C library. Native
methods will be disabled.".  Based on this warning, It looks like the .jar
file is actually on the classpath but the native access libraries still
aren't being used.

Does anyone know why I might be seeing this?  It's not a huge detriment to
our day-to-day operations but our backup strategy and BI strategy is largely
dependent on the ability to reliably create snapshots and make json
conversions so this is a big roadblock at the moment.  Any help would be
much appreciated.

Thank you!

--20cf307f3ac4fd077c04abd9e4d1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi everybody,=A0<div><br></div><div>I&#39;m running cassandra 0.7.5 on abou=
t 20 RHEL 5=A0(24 GB RAM)=A0machines and I&#39;m having issues with snapsho=
ts, json sstable conversions, and various nodetool commands due to memory e=
rrors and the lack of the native access C libraries. =A0I tried putting jna=
.jar on the classpath but I&#39;m still seeing warnings in the log files li=
ke &quot;CLibrary.java (line 65) Unable to link C library. Native methods w=
ill be disabled.&quot;. =A0Based on this warning, It looks like the .jar fi=
le is actually on the classpath but the native access libraries still aren&=
#39;t being used.</div>

<div><br></div><div>Does anyone know why I might be seeing this? =A0It&#39;=
s not a huge detriment to our day-to-day operations but our backup strategy=
 and BI strategy is largely dependent on the ability to reliably create sna=
pshots and make json conversions so this is a big roadblock at the moment. =
=A0Any help would be much appreciated.</div>

<div><br></div><div>Thank you!</div>

--20cf307f3ac4fd077c04abd9e4d1--