Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 6 Sep 2012 21:31:07 +1100 (NCT)
From: "Omid Aladini (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <2041812818.43702.1346927467757.JavaMail.jiratomcat@arcas>
In-Reply-To: <52138181.29232.1346628907777.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (CASSANDRA-4602) Stack Size on Sun JVM 1.6.0_33
 must be at least 160k
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-4602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13449551#comment-13449551 ] 

Omid Aladini commented on CASSANDRA-4602:
-----------------------------------------

Apparently this is due to HotSpot fix 7059899 [1] on 1.6.0_34 that increased "StackShadowPages"'s default to 20, since a change in socketWrite's native implementation required more stack space. Increased StackShadowPages might require increased stack size (-Xss) [2] so that upon a call to a native method, there would be at least "StackShadowPages" stack space available.

[1] http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7059899
[2] http://www.oracle.com/technetwork/java/javase/crashes-137240.html 
                
> 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
>         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
>            Assignee: Jonathan Ellis
>             Fix For: 1.0.12, 1.1.5
>
>         Attachments: 4602.txt
>
>
> 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