Aaron Morton created CASSANDRA-4602: ---------------------------------------
Summary: Stack Size on Sun JVM 1.6.0_33 must be at least 160k Key: CASSANDRA-4602 URL: https://issues.apache.org/jira/browse/CASSANDRA-4602 Project: Cassandra Issue Type: Bug Components: Core Affects Versions: 1.1.4 Environment: Ubuntu 10.04 java version "1.6.0_35" Java(TM) SE Runtime Environment (build 1.6.0_35-b10) Java HotSpot(TM) 64-Bit Server VM (build 20.10-b01, mixed mode) Reporter: Aaron Morton I started a fresh Cassandra 1.1.4 install with Sun JVM 1.6.35. On startup I got this in output.log {noformat} The stack size specified is too small, Specify at least 160k Cannot create Java VM Service exit with a return value of 1 {noformat} Remembering CASSANDRA-4275 I monkeyed around and started the JVM with -Xss160k the same as Java 7. I then got {code:java} ERROR [WRITE-/192.168.1.12] 2012-08-31 01:43:29,865 AbstractCassandraDaemon.java (line 134) Exception in thread Thread[WRITE-/192.168.1.12,5,main] java.lang.StackOverflowError at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(Unknown Source) at java.net.SocketOutputStream.write(Unknown Source) at java.io.BufferedOutputStream.flushBuffer(Unknown Source) at java.io.BufferedOutputStream.flush(Unknown Source) at java.io.DataOutputStream.flush(Unknown Source) at org.apache.cassandra.net.OutboundTcpConnection.writeConnected(OutboundTcpConnection.java:156) at org.apache.cassandra.net.OutboundTcpConnection.run(OutboundTcpConnection.java:126) {code} Same as CASSANDRA-4442 At which point I dropped back to Java 6.33. CASSANDRA-4457 bumped the stack size to 180 for java 7, should we also do this for Java 6.33+ ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira