Sure, here's the stack :
Client pipeline caught an exception
java.lang.NullPointerException
at io.netty.handler.codec.http2.DefaultHttp2RemoteFlowController.
maxUsableChannelBytes(DefaultHttp2RemoteFlowController.java:238)
at io.netty.handler.codec.http2.DefaultHttp2RemoteFlowController.
writableBytes(DefaultHttp2RemoteFlowController.java:250)
at io.netty.handler.codec.http2.DefaultHttp2RemoteFlowController.
access$900(DefaultHttp2RemoteFlowController.java:43)
at io.netty.handler.codec.http2.
DefaultHttp2RemoteFlowController$WritabilityMonitor.writePendingBytes(
DefaultHttp2RemoteFlowController.java:627)
at io.netty.handler.codec.http2.DefaultHttp2RemoteFlowController.
writePendingBytes(DefaultHttp2RemoteFlowController.java:255)
at io.netty.handler.codec.http2.Http2ConnectionHandler.flush(
Http2ConnectionHandler.java:161)
at io.netty.channel.AbstractChannelHandlerContext.invokeFlush0(
AbstractChannelHandlerContext.java:786)
at io.netty.channel.AbstractChannelHandlerContext.
invokeWriteAndFlush(AbstractChannelHandlerContext.java:812)
at io.netty.channel.AbstractChannelHandlerContext.write(
AbstractChannelHandlerContext.java:824)
at io.netty.channel.AbstractChannelHandlerContext.writeAndFlush(
AbstractChannelHandlerContext.java:804)
Could you instead add a listener on the future returned from writeAndFlush?
>
Same problem because the future returned by writeAndFlush is actually the
same as the promise you can use in the arguments.
Besides this behaviour could lead to tricky problems : if you add a
listener on writeAndFlush and then the future is completed with succes but
the flush() crash you won't be notified of this error (I mean you will be
with the exceptionCaught, but not with the promise).
Thanks for answer :)
Jonathan
--
You received this message because you are subscribed to the Google Groups
"Netty discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/netty/0963424a-882f-451b-88ef-e3ef5613d61c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
