Norman Maurer 9077acb6ab Correctly propagate exceptions from inbound operations in all cases (#10176) ... Motivation: In DefaultChannelHandlerContext we had some code where we tried to guard against endless loops caused by exceptions thrown by exceptionCaught(...) that would trigger exceptionCaught again. This code was proplematic for two reasons: - It is quite expensive as we need to compare all the stacks - We may end up not notify another handlers exceptionCaught(...) if in our exeuction stack we triggered actions that will cause an exceptionCaught somewhere else in the pipeline Modifications: - Just remove the detection code as we already handle everything correctly when we invoke exceptionCaught(...) - Add unit tests Result: Ensure we always notify correctly and also fixes performance issue reported as https://github.com/netty/netty/issues/10165		2020-04-16 09:07:48 +02:00
..
src	Correctly propagate exceptions from inbound operations in all cases (#10176)	2020-04-16 09:07:48 +02:00
pom.xml	Correcting Maven Dependencies (#8622)	2018-12-06 09:02:00 +01:00