# TooLongFrameException in ES logs **URL:** \ **Category:** Elasticsearch\ **Created:** [June 21, 2011, 5:04pm UTC](https://discuss.elastic.co/t/toolongframeexception-in-es-logs/4675 "2011-06-21T17:04:54Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Michael\_Korbakov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael_korbakov/32/3199_2.png) [@Michael\_Korbakov](https://discuss.elastic.co/u/Michael_Korbakov)\ **Post date:** [June 21, 2011, 5:04pm UTC](https://discuss.elastic.co/t/toolongframeexception-in-es-logs/4675/1 "2011-06-21T17:04:54Z")
Hi everyone. We're getting strange message in ES logs. Can't find anything about it in the mailing list. Could someone advice me what is it and how to handle it? [14:59:39,814][WARN][http.netty] [Slab] Caught exception while handling client http traffic, closing connection org.elasticsearch.common.netty.handler.codec.frame.TooLongFrameException: HTTP content length exceeded 104857600 bytes. at org.elasticsearch.common.netty.handler.codec.http.HttpChunkAggregator.messageReceived(HttpChunkAggregator.java:135) at org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80) at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:545) at org.elasticsearch.common.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:754) at org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:302) at org.elasticsearch.common.netty.handler.codec.replay.ReplayingDecoder.unfoldAndfireMessageReceived(ReplayingDecoder.java:522) at org.elasticsearch.common.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:506) at org.elasticsearch.common.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:443) at org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80) at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:545) at org.elasticsearch.common.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:754) at org.elasticsearch.common.netty.OpenChannelsHandler.handleUpstream(OpenChannelsHandler.java:51) at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:545) at org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:540) at org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:274) at org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:261) at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker.java:349) at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:280) at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:200) at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:44) 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) -- Michael Korbakov ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [June 23, 2011, 11:38am UTC](https://discuss.elastic.co/t/toolongframeexception-in-es-logs/4675/2 "2011-06-23T11:38:47Z")
There is a limit to the size of a single HTTP request size, set at 100mb. You can change that by setting: http.max\_content\_length. On Tuesday, June 21, 2011 at 8:04 PM, Michael Korbakov wrote: > Hi everyone. > > We're getting strange message in ES logs. Can't find anything about it in > the mailing list. Could someone advice me what is it and how to handle it? > > [14:59:39,814][WARN][http.netty] [Slab] Caught exception while handling > client http traffic, closing connection > org.elasticsearch.common.netty.handler.codec.frame.TooLongFrameException: > HTTP content length exceeded 104857600 bytes. > at > org.elasticsearch.common.netty.handler.codec.http.HttpChunkAggregator.messageReceived(HttpChunkAggregator.java:135) > at > org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80) > at > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:545) > at > org.elasticsearch.common.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:754) > at > org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:302) > at > org.elasticsearch.common.netty.handler.codec.replay.ReplayingDecoder.unfoldAndfireMessageReceived(ReplayingDecoder.java:522) > at > org.elasticsearch.common.netty.handler.codec.replay.ReplayingDecoder.callDecode(ReplayingDecoder.java:506) > at > org.elasticsearch.common.netty.handler.codec.replay.ReplayingDecoder.messageReceived(ReplayingDecoder.java:443) > at > org.elasticsearch.common.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:80) > at > org.elasticsearch.common.netty.channel.DefaultChannelPipeline..sendUpstream(DefaultChannelPipeline.java:545) > at > org.elasticsearch.common.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:754) > at > org.elasticsearch.common.netty.OpenChannelsHandler.handleUpstream(OpenChannelsHandler.java:51) > at > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:545) > at > org.elasticsearch.common.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:540) > at > org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:274) > at > org.elasticsearch.common.netty.channel.Channels.fireMessageReceived(Channels.java:261) > at > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker.java:349) > at > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:280) > at > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:200) > at > org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) > at > org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:44) > 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) > > -- Michael Korbakov > > -- > View this message in context: [http://elasticsearch-users.115913.n3.nabble.com/TooLongFrameException-in-ES-logs-tp3091727p3091727.html](http://elasticsearch-users.115913.n3.nabble.com/TooLongFrameException-in-ES-logs-tp3091727p3091727.html) > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com) ([http://Nabble.com](http://Nabble.com)). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 4:02am UTC](https://discuss.elastic.co/t/toolongframeexception-in-es-logs/4675/3 "2017-07-06T04:02:51Z")