Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of srisatish.ambati@gmail.com
 designates 209.85.214.44 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=Co7eIIYinomIct0irPGwV58ZbvlGhRj9oWafmCKDfnEJB4j1fWjlTHXk82ob3Telb9
         X9i+wgd2yrldXTrLc5qEWOMEmwXjpJOtETNECFfNP+0fjWjLdlT33EgaWb/v1DH184Uo
         AP+wwG7ivfwCpe5EgJJjMD3/T+UgRtPk5PobQ=
MIME-Version: 1.0
In-Reply-To: <AANLkTinNuAXW8n8_PpHswrLGxsoSD4Hc6Ad-9jAVgOr1@mail.gmail.com>
References: 
 <244a06a8-4f31-46b5-83f8-239ce2740cf4@j35g2000prb.googlegroups.com>
	<AANLkTinNuAXW8n8_PpHswrLGxsoSD4Hc6Ad-9jAVgOr1@mail.gmail.com>
Date: Sun, 20 Mar 2011 18:15:26 -0700
Message-ID: <AANLkTi=xyoJ50Zj_Wj++tN1meHP9S83MuDLPjt8kMN53@mail.gmail.com>
Subject: Re: Java segfault
From: SriSatish Ambati <srisatish.ambati@gmail.com>
To: user@cassandra.apache.org
Cc: Jonathan Ellis <jbellis@gmail.com>, Jason Harvey <alienth@gmail.com>
Content-Type: multipart/alternative; boundary=0016e6d7ef90e378b0049ef3dcd9

--0016e6d7ef90e378b0049ef3dcd9
Content-Type: text/plain; charset=ISO-8859-1

Indeed. This is likely at the JVM level.. (if not lower down the stack)

Do you happen to have a hs*err file for the crash? Is it reproducible?
What 'java -version"? What version of linux?

thanks,
Sri

On Sun, Mar 20, 2011 at 5:48 PM, Jonathan Ellis <jbellis@gmail.com> wrote:

> segfaults are either a JVM bug (are you on the latest Sun version?
> openjdk is very behind on fixes) or bad hardware.
>
> On Sun, Mar 20, 2011 at 7:17 PM, Jason Harvey <alienth@gmail.com> wrote:
> > Just ran into a Java segfault on 0.7.4 when Cassandra created a new
> > commitlog segment. Does that point to a bug in the JVM, or in
> > Cassandra? My guess would be the JVM, but I wanted to check before
> > submitting a bug report to anyone.
> >
> > Thanks!
> > Jason
> >
>
>
>
> --
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder of DataStax, the source for professional Cassandra support
> http://www.datastax.com
>

--0016e6d7ef90e378b0049ef3dcd9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Indeed. This is likely at the JVM level.. (if not lower down the stack)<br>=
<br>Do you happen to have a hs*err file for the crash? Is it reproducible? =
<br>What &#39;java -version&quot;? What version of linux?<br><br>thanks,<br=
>
Sri<br><br><div class=3D"gmail_quote">On Sun, Mar 20, 2011 at 5:48 PM, Jona=
than Ellis <span dir=3D"ltr">&lt;<a href=3D"mailto:jbellis@gmail.com">jbell=
is@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204);=
 padding-left: 1ex;">
segfaults are either a JVM bug (are you on the latest Sun version?<br>
openjdk is very behind on fixes) or bad hardware.<br>
<div><div></div><div class=3D"h5"><br>
On Sun, Mar 20, 2011 at 7:17 PM, Jason Harvey &lt;<a href=3D"mailto:alienth=
@gmail.com">alienth@gmail.com</a>&gt; wrote:<br>
&gt; Just ran into a Java segfault on 0.7.4 when Cassandra created a new<br=
>
&gt; commitlog segment. Does that point to a bug in the JVM, or in<br>
&gt; Cassandra? My guess would be the JVM, but I wanted to check before<br>
&gt; submitting a bug report to anyone.<br>
&gt;<br>
&gt; Thanks!<br>
&gt; Jason<br>
&gt;<br>
<br>
<br>
<br>
</div></div><font color=3D"#888888">--<br>
Jonathan Ellis<br>
Project Chair, Apache Cassandra<br>
co-founder of DataStax, the source for professional Cassandra support<br>
<a href=3D"http://www.datastax.com" target=3D"_blank">http://www.datastax.c=
om</a><br>
</font></blockquote></div><br>

--0016e6d7ef90e378b0049ef3dcd9--