[ 
https://issues.apache.org/jira/browse/CASSANDRA-5895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

John Sumsion updated CASSANDRA-5895:
------------------------------------

    Attachment: 0002-Ignoring-files-produced-by-ant-build.patch
                0001-Increasing-stack-size-to-avoid-error-on-OpenJDK-7-u4.patch

Here are two patches:
1) fix for this issue under JDK 1.7.0_40
2) fix for untracked files in git after running ant build

You can also fetch these from https://github.com/jdsumsion/cassandra (branch: 
jdk7-updates)
                
> JDK7 u40 stack size fixes
> -------------------------
>
>                 Key: CASSANDRA-5895
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5895
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>         Environment: cassandra, as launched by the default script by JDK 
> 1.7.0_40 using CCM
>            Reporter: John Sumsion
>         Attachments: 
> 0001-Increasing-stack-size-to-avoid-error-on-OpenJDK-7-u4.patch, 
> 0002-Ignoring-files-produced-by-ant-build.patch
>
>
> I use Archlinux, and the latest OpenJDK, and run my cassandra via @pcmanus's 
> ccm.
> When I tried the cassandra-2.0.0 branch via:
> {noformat}
> $ ccm create dev -v git:cassandra-2.0.0
> {noformat}
> Then when I say:
> {noformat}
> $ ccm populate -n3
> $ ccm node1 start -v
> {noformat}
> I get the following error:
> {noformat}
> xss =  -ea -javaagent:/home/blah/.ccm/repository/1.2.2/lib/jamm-0.2.5.jar 
> -XX:+UseThreadPriorities -XX:ThreadPriorityPolicy=42 -Xms1985M -Xmx1985M 
> -Xmn496M -XX:+HeapDumpOnOutOfMemoryError -Xss180k
> The stack size specified is too small, Specify at least 228k
> Error starting node node1
> Standard error output is:
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> {noformat}
> I tracked it down to conf/cassandra-env.sh, and changed the -Xss180k => 
> -Xss228k and the node started.

--
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

Reply via email to