So what precisely changed? You've got a custom build based on the jar name, which is perfectly reasonable, but what upgrade did you do? 2.2.5 to 2.2.6 ? Any other changes?
On 2017-07-20 05:41 (-0700), William Boutin <william.bou...@ericsson.com> wrote: > Thank you for your help. > We have been using jna-4.0.0.jar since using Cassandra 2.2(.6). Until last > week, we had no issues. Now, we are experiencing the exception that I > identified. We only have jna-4.0.0.jar loaded on our machines and the > CLASSPATH that Cassandra builds only uses the jar from the > /usr/share/cassandra/lib directory. Jna-3.2.4.jar was only introduced when I > was debugging the original issue and will never be loaded on our machines. > See the output of ps below. > > Should I be looking elsewhere? Some have brought up that low memory on a JVM > or LINUX machine could cause jar loading issues. I have tried doubling > -Xss256k to -Xss512k. > > Thanks > > Billy S. Boutin > Office Phone No. (913) 241-5574 > Cell Phone No. (732) 213-1368 > --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org For additional commands, e-mail: user-h...@cassandra.apache.org
