I've found this post describing the same problem. Unfortunately no answers:
https://www.mail-archive.com/[email protected]/msg03623.html

On 3 September 2014 18:58, Alberto Cordioli <[email protected]> wrote:
> Hi all,
>
> I searched for similar problems without any luck.
> I implemented a spout that continuously get this exception when
> emitting "more than a certain number of tuples". I was not able to
> understand how much this amount is, but I emit tuples in the order of
> millions per seconds.
> I've seen that other people had my same problem and resolved tuning
> the ack executors parameter. In my case I don't have ackers (disabled
> at spout level) and hence it couldn't related to this problem.
>
> The supervisor and nimbus logs look fine. The only problem I have is
> in the spout worker:
>
> java.io.IOException: Connection reset by peer
> at sun.nio.ch.FileDispatcherImpl.read0(Native Method) ~[na:1.7.0_65]
> at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) ~[na:1.7.0_65]
> at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) ~[na:1.7.0_65]
> at sun.nio.ch.IOUtil.read(IOUtil.java:192) ~[na:1.7.0_65]
> at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:379) 
> ~[na:1.7.0_65]
> at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:322)
> ~[netty-3.2.2.Final.jar:na]
> at 
> org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:281)
> ~[netty-3.2.2.Final.jar:na]
> at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:201)
> ~[netty-3.2.2.Final.jar:na]
> at 
> org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:46)
> [netty-3.2.2.Final.jar:na]
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> [na:1.7.0_65]
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> [na:1.7.0_65]
> at java.lang.Thread.run(Thread.java:745) [na:1.7.0_65]
>
> Does someone have an idea of why this happens?
>
> Thanks,
> Alberto
>
> --
> Alberto Cordioli



-- 
Alberto Cordioli

Reply via email to