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 Wed, 22 Mar 2017 21:08:42 GMT


Michael Kjellman commented on CASSANDRA-13333:

[~blerer] this looks great! Renaming {{CLibrary}} --> {{NativeLibrary}} helps make the
intent much clearer. 

# Should the loading of {{Native.register("winmm")}} in {{WindowsTimer}} also be moved into
# Looks like the trunk patch didn't get pushed up or potentially just a copy paste error?
Currently it's just pointing at blerer/trunk.
# Thanks for putting the MSDN API URL in the method javadoc. :)
# In {{NativeLibraryWindows}} I think the following logger statements could be simplified:

catch (UnsatisfiedLinkError e)
    logger.warn("JNA link failure, one or more native method will be unavailable.");
    logger.error("JNA link failure details: {}", e.getMessage());

Can be simplified to:
logger.error("Failed to link against JNA. Native methods will be unavailable.", e);

> 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