[
https://issues.apache.org/jira/browse/CASSANDRA-4275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283533#comment-13283533
]
Jonathan Ellis commented on CASSANDRA-4275:
-------------------------------------------
bq. there must be some fairly major underlying factor that made the JVM
developers decided to raise the minimum allowable from whatever it was to 160
Doubt it. Old minimum was 128, so it's not *that* big a change.
I've asked Jake Farrell to have a look at Thrift/Java7 to see if anything odd
is going on here.
> 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
> 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
