incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Schuller <peter.schul...@infidyne.com>
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>(HeapByteBuffer.java:39)
>        at java.nio.ByteBuffer.allocate(ByteBuffer.java:312)
>        at org.apache.cassandra.utils.FBUtilities.readByteArray(FBUtilities.java:261)
>        at org.apache.cassandra.db.ColumnSerializer.deserialize(ColumnSerializer.java:76)
>        at org.apache.cassandra.db.ColumnSerializer.deserialize(ColumnSerializer.java:35)
>        at org.apache.cassandra.db.ColumnFamilySerializer.deserializeColumns(ColumnFamilySerializer.java:129)
>        at org.apache.cassandra.db.ColumnFamilySerializer.deserialize(ColumnFamilySerializer.java:120)
>        at org.apache.cassandra.db.RowMutationSerializer.defreezeTheMaps(RowMutation.java:383)
>        at org.apache.cassandra.db.RowMutationSerializer.deserialize(RowMutation.java:393)
>        at org.apache.cassandra.db.RowMutationSerializer.deserialize(RowMutation.java:351)
>        at org.apache.cassandra.db.RowMutationVerbHandler.doVerb(RowMutationVerbHandler.java:52)
>        at org.apache.cassandra.net.MessageDeliveryTask.run(MessageDeliveryTask.java:63)
>        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
>        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
>        at java.lang.Thread.run(Thread.java:662)

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. ColumnFamilySerializer.java:129 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

Mime
View raw message