An existing connection was forcibly closed by the remote host
neilson9
neil at liquidlabs.co.uk
Fri Jul 3 03:44:17 EDT 2009
Hi,
Ive been testing netty (CR2 nightly snapshot) for the last few weeks after
integrating it into our environment. At a stage
where we experience a burst of traffic - 70-100 machines all establish
connections to stream results, we end with many of the experiencing
'existing connection was forcibly closed by the remote host' (as below) -
its only during this short burst where the exception is experienced. We also
have retry logic to throw the existing conection establish a new one - they
do eventually get through but also experience subsequent exceptions.
The environment is a series of windows machines -the main servers nodes are
Windows2003Server (Ive upped the Tcpip.sys to 2000) - and while monitoring
the network we peak at 1095 connections.
I would have thought this number of connections wouldnt be a problem - is
this a windows OS problem or something I can work around, or tune in Netty?
Regards Neil.
platform: java6u13, Win2003serverSP1, Netty 3.1CR2 snapshot from last week
1666, 2009-07-03 08:15:26,290 WARN New I/O client worker #2-3
(netty.NettyClientHandler)
com.liquidlabs.transport.netty.NettyClientHandler at 1c05149 m:null
Client[null]
TalkingTo[stcp://LONMS02003:10005/_startTime=1246551675395&udp=0]
Channel[[id: 0x013aaba7, /0.0.0.0:4680 => LONMS02003/172.26.32.245:10005]]
Unexpected exception from downstream, latch[null]
1667, java.io.IOException: An existing connection was forcibly closed by the
remote host
1668, at sun.nio.ch.SocketDispatcher.read0(Native Method)
1669, at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:25)
1670, at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:233)
1671, at sun.nio.ch.IOUtil.read(IOUtil.java:206)
1672, at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:236)
1673, at
org.jboss.netty.buffer.HeapChannelBuffer.setBytes(HeapChannelBuffer.java:163)
1674, at
org.jboss.netty.buffer.AbstractChannelBuffer.writeBytes(AbstractChannelBuffer.java:432)
1675, at
org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:312)
1676, at
org.jboss.netty.channel.socket.nio.NioWorker.processSelectedKeys(NioWorker.java:282)
1677, at
org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:203)
1678, at
org.jboss.netty.util.internal.IoWorkerRunnable.run(IoWorkerRunnable.java:53)
1679, at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
1680, at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
1681, at java.lang.Thread.run(Thread.java:619)
--
View this message in context: http://n2.nabble.com/An-existing-connection-was-forcibly-closed-by-the-remote-host-tp3199960p3199960.html
Sent from the Netty User Group mailing list archive at Nabble.com.
More information about the netty-users
mailing list