Kevin Wu 54bfd21e52 Fix #10434 OutOfDirectMemoryError causes cpu load too high and socket is full (#10457) ... Motivation: When we were using the netty http protocol, OOM occurred, this problem has been in 4.1.51.Final Fix [# 10424](https://github.com/netty/netty/issues/10424), even if OOM is up, the service will still receive new connection events, will occur again OOM and eventually cause the connection not to be released. code `byteBuf = allocHandle.allocate(allocator);` Modification: I fail to create buffer when I try to receive new data, i determine if it is OOM then the close read event releases the connection. ```java if (close || cause instanceof OutOfMemoryError || cause instanceof IOException) { closeOnRead(pipeline); } ``` Result: Fixes # [10434](https://github.com/netty/netty/issues/10434).		2020-08-13 10:14:19 +02:00
..
src	Fix #10434 OutOfDirectMemoryError causes cpu load too high and socket is full (#10457)	2020-08-13 10:14:19 +02:00
pom.xml	[maven-release-plugin] prepare for next development iteration	2020-07-09 12:27:06 +00:00