[
https://issues.apache.org/jira/browse/FLUME-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14032252#comment-14032252
]
chenshangan commented on FLUME-2404:
------------------------------------
Exception stack is as following:
16 Jun 2014 15:03:10,526 ERROR [Thread-2]
(org.apache.thrift.server.TNonblockingServer$SelectThread.run:247) - run()
exiting due to uncaught error
java.lang.OutOfMemoryError: Java heap space
at java.nio.HeapByteBuffer.<init>(HeapByteBuffer.java:57)
at java.nio.ByteBuffer.allocate(ByteBuffer.java:331)
at
org.apache.thrift.server.TNonblockingServer$FrameBuffer.read(TNonblockingServer.java:491)
at
org.apache.thrift.server.TNonblockingServer$SelectThread.handleRead(TNonblockingServer.java:359)
at
org.apache.thrift.server.TNonblockingServer$SelectThread.select(TNonblockingServer.java:304)
at
org.apache.thrift.server.TNonblockingServer$SelectThread.run(TNonblockingServer.java:243)
> Default maxReadBufferBytes might cause OOM and cause scribe source exit
> -----------------------------------------------------------------------
>
> Key: FLUME-2404
> URL: https://issues.apache.org/jira/browse/FLUME-2404
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Affects Versions: v1.5.0
> Reporter: chenshangan
> Assignee: chenshangan
>
> We're using scribe source, some hacker like infosec guys send some malicious
> frames to flume with the frame size field set to a very big integer, then the
> thrift server inside scribe source will exit due to OOM. Then scribe source
> will keep wait_close state and can not accept any connection.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
