Cassandra appears to hang when JNA enabled and heapsize > free memory
---------------------------------------------------------------------
Key: CASSANDRA-4104
URL: https://issues.apache.org/jira/browse/CASSANDRA-4104
Project: Cassandra
Issue Type: Bug
Affects Versions: 1.0.8
Reporter: Joaquin Casares
Priority: Minor
When JNA is enabled heapsize is larger than free memory, all that is printed
out is the classpath, then the printouts stop.
If you hit enter again, you get the commandline, but no Cassandra process is
running.
Tested on both OpenJDK and Oracle Java.
{noformat}
datastax@datastax-image:~/repos/cassandra$ free -m
total used free shared buffers cached
Mem: 2008 740 1267 0 3 54
-/+ buffers/cache: 682 1326
Swap: 0 0 0
datastax@datastax-image:~/repos/cassandra$ sudo bin/cassandra
datastax@datastax-image:~/repos/cassandra$ INFO 14:31:32,520 Logging
initialized
INFO 14:31:32,533 JVM vendor/version: Java HotSpot(TM) 64-Bit Server
VM/1.6.0_31
INFO 14:31:32,534 Heap size: 1247805440/1247805440
INFO 14:31:32,534 Classpath:
bin/../conf:bin/../build/classes/main:bin/../build/classes/thrift:bin/../lib/antlr-3.2.jar:bin/../lib/avro-1.4.0-fixes.jar:bin/../lib/avro-1.4.0-sources-fixes.jar:bin/../lib/commons-cli-1.1.jar:bin/../lib/commons-codec-1.2.jar:bin/../lib/commons-lang-2.4.jar:bin/../lib/compress-lzf-0.8.4.jar:bin/../lib/concurrentlinkedhashmap-lru-1.2.jar:bin/../lib/guava-r08.jar:bin/../lib/high-scale-lib-1.1.2.jar:bin/../lib/jackson-core-asl-1.4.0.jar:bin/../lib/jackson-mapper-asl-1.4.0.jar:bin/../lib/jamm-0.2.5.jar:bin/../lib/jline-0.9.94.jar:bin/../lib/jna.jar:bin/../lib/json-simple-1.1.jar:bin/../lib/libthrift-0.6.jar:bin/../lib/log4j-1.2.16.jar:bin/../lib/servlet-api-2.5-20081211.jar:bin/../lib/slf4j-api-1.6.1.jar:bin/../lib/slf4j-log4j12-1.6.1.jar:bin/../lib/snakeyaml-1.6.jar:bin/../lib/snappy-java-1.0.4.1.jar:bin/../lib/jamm-0.2.5.jar
datastax@datastax-image:~/repos/cassandra$ ps auwx | grep cass
datastax 18374 1.0 0.0 13448 904 pts/2 S+ 14:32 0:00 grep
--color=auto cass
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
