netty5/transport
Norman Maurer e847ac0443 Fix possible deadlock in DefaultChannelPipeline.destroyDown(...)
Motivation:

We need to ensure we not hold a lock while executor callHandlerRemoved(...) as this may lead to a deadlock if handlerRemoved(...) will call another method in DEfaultChannelPipeline from another thread that will need to obtain the lock as well and wait for the result.

Modifications:

Release the lock before call handlerRemoved0(...).

Result:

No more deadlock possible
2016-06-04 09:13:54 +02:00
..
src Fix possible deadlock in DefaultChannelPipeline.destroyDown(...) 2016-06-04 09:13:54 +02:00
pom.xml [maven-release-plugin] prepare for next development iteration 2016-05-25 19:16:44 +02:00