[
https://issues.apache.org/jira/browse/CASSANDRA-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis resolved CASSANDRA-1671.
---------------------------------------
Resolution: Not A Problem
See discussion at
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/using-jna-jar-Unknown-mlockall-error-0-tp5614316p5614316.html
> Unknown mlockall error 0
> -------------------------
>
> Key: CASSANDRA-1671
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1671
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7 beta 2
> Environment: CentOS5.4
> JNA-3.2.7
> Reporter: Arya Goudarzi
>
> Using JNA-3.2.7, when a single node fires up, the very first complain is this:
> Unknown mlockall error 0
> I am not sure if this poses any problem. I checked on IRC and hermes also has
> the same message when he restart his server.
> Please advice.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
