StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PONetty pipeline warning
text
Body
copied!<p>Netty 4 issues a warning "Discarded 1 inbound message(s) that reached at the end of the pipeline. Please check your pipeline configuration". What does it mean? how should it be handled? (previously <a href="https://github.com/cloudaloe/pipe" rel="nofollow">reproduced here</a> until solved per the accepted answer, but I'd rather have the general explanation about what does it mean and how the pipeline works)</p> <p>Trying to max out netty feedback, the client-side pipeline is set as follows:</p> <pre><code>pipeline.addLast("logger", new LoggingHandler(LogLevel.TRACE)) pipeline.addLast("HttpRequestEncoder", new HttpClientCodec) pipeline.addLast("handler", new myHandler) </code></pre> <p>All I'm getting logged on the client-side by Netty while two http messages are sent by it and successfully received and acknowledged by the server side is:</p> <pre><code>12 [main] DEBUG io.netty.util.internal.InternalLoggerFactory - Using Log4J as the default logging framework 164 [nioEventLoopGroup-1-2] DEBUG io.netty.channel.nio.SelectorUtil - Using select timeout of 500 164 [nioEventLoopGroup-1-2] DEBUG io.netty.channel.nio.SelectorUtil - Epoll-bug workaround enabled = false 229 [nioEventLoopGroup-1-2] WARN io.netty.channel.DefaultChannelPipeline - Discarded 1 inbound message(s) that reached at the end of the pipeline. Please check your pipeline configuration. 230 [nioEventLoopGroup-1-2] WARN io.netty.channel.DefaultChannelPipeline - Discarded 1 inbound message(s) that reached at the end of the pipeline. Please check your pipeline configuration. </code></pre> <p>Whereas logging is set up minimally as so:</p> <pre><code>BasicConfigurator.configure InternalLoggerFactory.setDefaultFactory(new Log4JLoggerFactory) </code></pre>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload