[
https://issues.apache.org/jira/browse/CASSANDRA-4275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13419894#comment-13419894
]
Jeremy Hanna commented on CASSANDRA-4275:
-----------------------------------------
Fair enough. A clear notification would be nice so that they know to update
the value without checking the user list or IRC. It sounds like Ed and others
are starting to use JDK7 in production based on the needs of their
organization, so it would be nice to have something documented about support
for JDK7 and tweaking as you've mentioned.
> 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: Sylvain Lebresne
> Fix For: 1.1.2
>
> Attachments: 4275.txt, trunk-cassandra-4275.1.patch.txt,
> v1-0001-CASSANDRA-4275-Use-JVM-s-reported-minimum-stack-size-o.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
