netty5/transport
Nick Hill 00a9a25f29 Ensure channel handler close() is not skipped in !hasDisconnect case (#9098)
Motivation

The optimization in #8988 didn't correctly handle the specific case
where the channel hasDisconnect == false, and a
ChannelOutboundHandlerAdapter subclass overrides only the close(ctx,
promise) method without also overriding the disconnect(ctx, promise)
method.

Modifications

Adjust AbstractChannelHandler.disconnect(...) method to divert to
close(...) in !hasDisconnect case before computing target context for
the event.

Result

Fixes #9092
2019-04-28 10:41:51 +02:00
..
src Ensure channel handler close() is not skipped in !hasDisconnect case (#9098) 2019-04-28 10:41:51 +02:00
pom.xml [maven-release-plugin] prepare for next development iteration 2019-04-17 07:26:24 +00:00