Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 52576 invoked from network); 14 Dec 2010 20:07:57 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 14 Dec 2010 20:07:57 -0000 Received: (qmail 47328 invoked by uid 500); 14 Dec 2010 20:07:55 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 47307 invoked by uid 500); 14 Dec 2010 20:07:55 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 47299 invoked by uid 99); 14 Dec 2010 20:07:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Dec 2010 20:07:55 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.213.172] (HELO mail-yx0-f172.google.com) (209.85.213.172) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Dec 2010 20:07:45 +0000 Received: by yxt33 with SMTP id 33so660022yxt.31 for ; Tue, 14 Dec 2010 12:07:22 -0800 (PST) MIME-Version: 1.0 Received: by 10.150.138.2 with SMTP id l2mr8619425ybd.261.1292357241952; Tue, 14 Dec 2010 12:07:21 -0800 (PST) Sender: scode@scode.org Received: by 10.150.220.9 with HTTP; Tue, 14 Dec 2010 12:07:21 -0800 (PST) X-Originating-IP: [213.114.156.79] In-Reply-To: <560C1FD8-6997-45F9-A8AE-98431CFB5DF7@toptarif.de> References: <43B93B23-D289-481A-8C69-8BCB866ADFF9@toptarif.de> <2E5D89FA-274D-4811-8EE5-BD389FB0E015@toptarif.de> <7F6C35CA-70C0-456E-AB9D-9DC883576DC1@toptarif.de> <560C1FD8-6997-45F9-A8AE-98431CFB5DF7@toptarif.de> Date: Tue, 14 Dec 2010 21:07:21 +0100 X-Google-Sender-Auth: _vINVN3Kj7pwWglbxtg4ufjyjYU Message-ID: Subject: Re: Memory leak with Sun Java 1.6 ? From: Peter Schuller To: user@cassandra.apache.org Content-Type: text/plain; charset=UTF-8 >> The stack trace doesn't make sense relative to what I get checking out >> 0.6.6. Are you *sure* this is 0.6.6, without patches or other changes? > > Oh, sorry, the original poster of this thread was/is actually using 0.6, I am (as mentioned in other posts) actually on 0.7rc2. Sorry that I didn't point this out once again. Sorry, my bad. I tend to catch up on the ML:s during transportation to/from work and is in 'fast sifting' mode ;) Sometimes multiple people from the same group/org/company posts int he same thread about the same issue and I thought this was the case here. In that case, based on the strack trace, I wonder if you're hitting what I was hitting just yesterday/earlier today: https://issues.apache.org/jira/browse/CASSANDRA-1860 Which is suspected (currently being tested that it's gone with updated 0.7) to be due to: https://issues.apache.org/jira/browse/CASSANDRA-1847 If the corruption happens to be slightly different in your case, maybe it just ends up trying to allocate a large array instead of the failure mode I got (EOF or bad cfId) on the receiving end. Can you try to reproduce with the latest 0.7 branch as of today? It seems very similar in nature at least based on the latest stack trace. -- / Peter Schuller