[
https://issues.apache.org/jira/browse/CASSANDRA-13333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930006#comment-15930006
]
Benjamin Lerer commented on CASSANDRA-13333:
--------------------------------------------
Then does it really make sense to keep the {{jnaAvailable()}} method? Right
now, that check does not really bring much because if the library cannot be
linked the server will start anyway.
Is a warning in the log not enough? I really wonder if anybody is really using
the NativeMBean to check that jna and mlock are available.
[~jasobrown], [~mkjellman] what is your opinion on that?
> 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)