ERROR 23:50:24,264 Uncaught exception in thread Thread[pool-1-thread-5,5,main]
------------------------------------------------------------------------------
Key: CASSANDRA-1245
URL: https://issues.apache.org/jira/browse/CASSANDRA-1245
Project: Cassandra
Issue Type: Bug
Affects Versions: 0.6.3
Environment: Mac OS Snow Leopard 10.6.4
Reporter: Pedro Paixao
Priority: Minor
When connecting with cassandra-cli after enabling
<ThriftFramedTransport>true</ThriftFramedTransport> in storage-conf.xml the
cassandra daemon crashes with
java.lang.OutOfMemoryError: Java heap space
Dumping heap to java_pid95320.hprof ...
Heap dump file created [4638171 bytes in 0.542 secs]
ERROR 23:50:24,264 Uncaught exception in thread Thread[pool-1-thread-5,5,main]
java.lang.OutOfMemoryError: Java heap space
at
org.apache.thrift.protocol.TBinaryProtocol.readStringBody(TBinaryProtocol.java:296)
at
org.apache.thrift.protocol.TBinaryProtocol.readMessageBegin(TBinaryProtocol.java:203)
at
org.apache.cassandra.thrift.Cassandra$Processor.process(Cassandra.java:1116)
at
org.apache.cassandra.thrift.CustomTThreadPoolServer$WorkerProcess.run(CustomTThreadPoolServer.java:167)
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:637)
if I use the --framed option in cassandra-cli it works. I know it is supposed
to work only with the --framed option, but the daemon should not crash just
because a user forgets to use the --framed option to cassandra-cli.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
