[
https://issues.apache.org/jira/browse/CASSANDRA-4275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281703#comment-13281703
]
Peter Schuller commented on CASSANDRA-4275:
-------------------------------------------
Just wanted to quickly chime in and say that I saw this too at 160k (used 512k
and was done with it). I don't remember whether the stack trace matches exactly
or not, but it was definitely one of the I/O paths - either thrift or
internode. This was with a build of openjdk7, so not specific to the Oracle
release.
> Oracle Java 1.7 u4 does not allow Xss128k
> -----------------------------------------
>
> Key: CASSANDRA-4275
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4275
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.9, 1.1.0
> Reporter: Edward Capriolo
> Assignee: Edward Capriolo
> Attachments: trunk-cassandra-4275.1.patch.txt
>
>
> Problem: This happens when you try to start it with default Xss setting of
> 128k
> =======
> The stack size specified is too small, Specify at least 160k
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> Solution
> =======
> Set -Xss to 256k
> Problem: This happens when you try to start it with Xss = 160k
> ========
> ERROR [Thrift:14] 2012-05-22 14:42:40,479 AbstractCassandraDaemon.java (line
> 139) Fatal exception in thread Thread[Thrift:14,5,main]
> java.lang.StackOverflowError
> Solution
> =======
> Set -Xss to 256k
--
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
