[
https://issues.apache.org/jira/browse/CASSANDRA-13333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928895#comment-15928895
]
Michael Kjellman commented on CASSANDRA-13333:
----------------------------------------------
[~blerer] I don't have a Windows machine to test this unfortunately... but, I
do know what's going on, although I'm not sure about the correct fix.
The following code from {{StartupChecks}}:
{code}
public static final StartupCheck checkJnaInitialization = new StartupCheck()
{
public void execute() throws StartupException
{
// Fail-fast if JNA is not available or failing to initialize
properly
if (!CLibrary.jnaAvailable())
throw new
StartupException(StartupException.ERR_WRONG_MACHINE_STATE, "JNA failing to
initialize properly. ");
}
};
{code}
This is due to the fact that when I implemented the Windows {{CLibraryWrapper}}
implementation {{CLibraryWindows}}, I had it return false for jnaAvailable().
Given that we only use JNA right now to access libc calls I wasn't aware that
any of those would be implemented in JNA to do something in Windows.
If that's not correct, I'll throw a very quick patch together to load JNA in
the Windows implementation, but I'll still need some help to know what wrapped
methods actually work on Windows.
Should the startup check just be exempted for Windows?
> Cassandra does not start on Windows due to 'JNA link failure'
> -------------------------------------------------------------
>
> Key: CASSANDRA-13333
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13333
> 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
(v6.3.15#6346)
