[
https://issues.apache.org/jira/browse/CAMEL-9335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15010423#comment-15010423
]
Claus Ibsen commented on CAMEL-9335:
------------------------------------
{code}
2015-11-13 07:48:18,601 [ntExecutorGroup] WARN NettyHttpConsumer
- Closing channel as an exception was thrown from Netty
java.io.IOException: Connection reset by peer
at sun.nio.ch.FileDispatcherImpl.read0(Native Method)
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
at sun.nio.ch.IOUtil.read(IOUtil.java:192)
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
at
io.netty.buffer.UnpooledUnsafeDirectByteBuf.setBytes(UnpooledUnsafeDirectByteBuf.java:447)
at io.netty.buffer.AbstractByteBuf.writeBytes(AbstractByteBuf.java:881)
at
io.netty.channel.socket.nio.NioSocketChannel.doReadBytes(NioSocketChannel.java:241)
at
io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:119)
at
io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:511)
at
io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:468)
at
io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:382)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:354)
at
io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:111)
at java.lang.Thread.run(Thread.java:745)
{code}
> camel-netty-http - Suppress Connection reset by peer WARNs
> ----------------------------------------------------------
>
> Key: CAMEL-9335
> URL: https://issues.apache.org/jira/browse/CAMEL-9335
> Project: Camel
> Issue Type: Improvement
> Components: camel-netty-http, camel-netty4-http
> Affects Versions: 2.16.0
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.16.1, 2.15.5, 2.17.0
>
>
> Due to various reasons a remote connection may close and you can end up
> having WARN logs on the netty http server side. We should suppress these logs
> and do them on a DEBUG level instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
