cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Schuller <>
Subject Re: Memory leak with Sun Java 1.6 ?
Date Tue, 14 Dec 2010 18:45:46 GMT
> java.lang.OutOfMemoryError: Java heap space
>        at java.nio.HeapByteBuffer.<init>(
>        at java.nio.ByteBuffer.allocate(
>        at org.apache.cassandra.utils.FBUtilities.readByteArray(
>        at org.apache.cassandra.db.ColumnSerializer.deserialize(
>        at org.apache.cassandra.db.ColumnSerializer.deserialize(
>        at org.apache.cassandra.db.ColumnFamilySerializer.deserializeColumns(
>        at org.apache.cassandra.db.ColumnFamilySerializer.deserialize(
>        at org.apache.cassandra.db.RowMutationSerializer.defreezeTheMaps(
>        at org.apache.cassandra.db.RowMutationSerializer.deserialize(
>        at org.apache.cassandra.db.RowMutationSerializer.deserialize(
>        at org.apache.cassandra.db.RowMutationVerbHandler.doVerb(
>        at
>        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
>        at java.util.concurrent.ThreadPoolExecutor$
>        at

Still 0.6.6 right?

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?

Maybe I'm making some kind of mistake, but on "my" 0.6.6 the above
doesn't jive. E.g. is an empty line
between two try blocks.

I want to see what buffer allocation is triggering this to judge
whether a large allocation could be driven by a legitimate large
value, or whether it is something completely different that might
indicate some kind of on-the-wire or in-memory corruption.

/ Peter Schuller

View raw message