Without more information, it's hard to say for sure, but my guess would be one of the following:
1) your java heap size (-Xmx) is too low for the size of messages you are sending 2) you are sending random traffic to your thrift server's port that happens to look like an oversized message. some port monitoring tools do things like this. On Mon, Oct 18, 2010 at 7:48 PM, JKnight JKnight <[email protected]>wrote: > Dear all, > I have error with Thrift. > Cound you help me to fix this bug? > > ERROR [Thread-1] 2010-10-19 08:43:49,551 FilterDaemon.java (line 58) Fatal > exception in thread Thread[Thread-1,5,main] > 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.thrift.server.TNonblockingServer$FrameBuffer.read(TNonblockingServer.java:541) > at > > org.apache.thrift.server.TNonblockingServer$SelectThread.handleRead(TNonblockingServer.java:412) > at > > org.apache.thrift.server.TNonblockingServer$SelectThread.select(TNonblockingServer.java:357) > at > > org.apache.thrift.server.TNonblockingServer$SelectThread.run(TNonblockingServer.java:301) > > Thank a lot for support. > -- > Best regards, > JKnight >
