netty5/transport
Norman Maurer 250e2494d9
Only call handlerRemoved(...) if handlerAdded(...) was called during adding the handler to the pipeline. (#8684)
Motivation:

Due a race in DefaultChannelPipeline / AbstractChannelHandlerContext it was possible to have only handlerRemoved(...) called during tearing down the pipeline, even when handlerAdded(...) was never called. We need to ensure we either call both of none to guarantee a proper lifecycle of the handler.

Modifications:

- Enforce handlerAdded(...) / handlerRemoved(...) semantics / ordering
- Add unit test.

Result:

Fixes https://github.com/netty/netty/issues/8676 / https://github.com/netty/netty/issues/6536 .
2019-01-14 08:19:48 +01:00
..
src Only call handlerRemoved(...) if handlerAdded(...) was called during adding the handler to the pipeline. (#8684) 2019-01-14 08:19:48 +01:00
pom.xml Correcting Maven Dependencies (#8622) 2018-12-06 09:01:14 +01:00
test.log Correctly implement SelectedSelectionKeySet.Iterator remove() 2018-09-01 08:59:08 +02:00