cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Kjellman (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13333) Cassandra does not start on Windows due to 'JNA link failure'
Date Tue, 21 Mar 2017 21:13:41 GMT


Michael Kjellman commented on CASSANDRA-13333:


* Just chatted quickly with [~jasobrown] and [~jjirsa] and I think hiding the fact we're using
JNA under the hood and going with {{isAvailable()}} vs. {{jnaAvailable()}] is a good change,
however, I think that changes the scope a bit. In the case of {{CLibraryWindows}} I used the
existing Sigar based logic to get the current PID of the running JVM as I wasn't sure if the
*nix APIs would work in Windows land. Thinking about it, this means {{isAvailable()}} is a
bit more nuanced. For instance, in the current {{CLibraryWindows}} case, yes, the {{callGetpid()}}
method is "available" but all the other methods that we happen to have right now use JNA,
which isn't "available" in the Windows case.
* Do you happen to know if the native {{getpid()}} JNA will work on Windows? If so we can
switch that from Sigar -> JNA for Windows too just like we're already doing for the Linux/Darwin
case. If so, it makes sense to attempt to load JNA and libc in the WIndows case too?
* I don't think we should remove the checkJnaInitialization {{StartupCheck}} at minimum in
the Linux and Darwin cases. Given that we ship JNA in the release, either we can't link against
the library it due to an issue or someone removed it. Given the performance implications I
think we should leave the hard fail in place -- but skip it if the current OS type is  Windows.

> Cassandra does not start on Windows due to 'JNA link failure'
> -------------------------------------------------------------
>                 Key: CASSANDRA-13333
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Benjamin Lerer
>            Assignee: Benjamin Lerer
>            Priority: Blocker
> Cassandra 3.0 HEAD does not start on Windows. The only error in the logs is: 
> {{ERROR 16:30:10 JNA failing to initialize properly.}} 

This message was sent by Atlassian JIRA

View raw message