netty5/handler
Norman Maurer 6dbec4181c Ensure we not complete the same promise that may be failed because of outbound handler exception.
Motivation:

It's important that we do not pass in the original ChannelPromise to safeClose(...) as when flush(...) will throw an Exception it will be propagated to the AbstractChannelHandlerContext which will try to fail the promise because of this. This will then fail as it was already completed by safeClose(...).

Modifications:

Create a new ChannelPromise and pass it to safeClose(...).

Result:

No more confusing logs because of failing to fail the promise.
2016-12-01 21:20:03 +01:00
..
src Ensure we not complete the same promise that may be failed because of outbound handler exception. 2016-12-01 21:20:03 +01:00
pom.xml [maven-release-plugin] prepare for next development iteration 2016-10-14 13:20:41 +02:00