Closed knosach closed 7 years ago
According the client ticket: 34226, the same problem happen due to Recording file size.
@knosach any progress on this one ? @leftyb we can increase the default limit in cloud as @knosach mentioned to me in India as a quick workaround
@deruelle added JUnit test https://github.com/RestComm/load-balancer/commit/61aca0c1ce437b8dacea56ff1a1a0ce25d090201
tickets 34139 We are observing following exception frequently in LB logs: it looks like a http response is too big for netty to carry forward. We should print HTTP request & response with this exception so we know nature of the message and work more on that. org.jboss.netty.handler.codec.frame.TooLongFrameException: HTTP content length exceeded 2097152 bytes. at org.jboss.netty.handler.codec.http.HttpChunkAggregator.messageReceived(HttpChunkAggregator.java:169) at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296)