cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Malte Pickhan (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-8927) Mark libjna-java + libjna-jni as incompatible in debian package
Date Thu, 14 Jan 2016 14:28:40 GMT


Malte Pickhan commented on CASSANDRA-8927:

Actually I currently hit exactly this issue, is there any advice as workaround.

I get the following error during startup:

There is an incompatible JNA native library installed on this system
To resolve this issue you may do one of the following:
 - remove or uninstall the offending library
 - set the system property jna.nosys=true
 - set jna.boot.library.path to include the path to the version of the 
   jnidispatch library included with the JNA jar file you are using

As far as i understood adding `jna.nosys=true` to the might have the implication
that cassandra is unable to allocate more memory.

> Mark libjna-java + libjna-jni as incompatible in debian package
> ---------------------------------------------------------------
>                 Key: CASSANDRA-8927
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Packaging
>         Environment: Debian
>            Reporter: Robert Stupp
>            Assignee: Michael Shuler
>            Priority: Minor
>             Fix For: 3.0.x
> Current Debian (Wheezy) might bring {{libjna-java}} in version 3.2.7-4, which has incompatible
{{}} because since C* 2.1 we use JNA 4.0.0 (the native stuff changed):
> jna.jar includes all binaries for all supported platforms - so there's no need for libjna
installed separately.
> Since CASSANDRA-8714 has been committed, the incompatibility manifests in {{java.lang.NoClassDefFoundError:
Could not initialize class com.sun.jna.Native}} (which is caused by outdated libjna-java installed
via apt).
> Note: Debian jessie adds new package {{libjna-jni}} (4.1.0-1) in addition to {{libjna-java}}
(4.1.0-1) - both contain the {{}}. Although these seem to work, we might
hit the same issue when there's a need to upgrade JNA to 4.2.x sometime.

This message was sent by Atlassian JIRA

View raw message