here's the deal, the error is on the receiving side. ie, the server printing the error is the on the receiving side getting data. So the sending server closes its connections, and the receiving server prints this message. If the network times out, then this is fine, its more an info message than severe, but it could also be telling you that your network wont allow TCP connections to stay open. and for that, there is no setting inside tomcat.
if you do find an option that you would need to set, but its not available, just let us know and we'll expose it for you. Filip ----- Original Message ----- From: "Ronald Klop" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Tuesday, November 09, 2004 2:09 PM Subject: Re: exception in clustering Yes, I understand that, but I was wondering if there is more experience with using a cluster under load. I am thinking about timeout settings? Or maybe something else. I have everything as default now. Ronald. On Tue Nov 09 17:21:47 CET 2004 Filip Hanik - Dev <[EMAIL PROTECTED]> wrote: > looks pretty normal, this shows that a connection was broken between one > server and the other, > you need to figure out why it breaks? restart? network? > > Filip > > ----- Original Message ----- > From: "Ronald Klop" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, November 09, 2004 10:02 AM > Subject: exception in clustering > > > Hello, > > I've a cluster of two nodes with 5.0.25 running on Linux. > Everythings works fine for most of the day, but we are now getting this a lot > on one server. > After shutting down this server, the other one still runs. > > Nov 9, 2004 4:50:24 PM org.apache.catalina.cluster.tcp.TcpReplicationThread > run > SEVERE: TCP Worker thread in cluster caught 'java.io.IOException: Connection > reset by peer' closing channel > java.io.IOException: Connection reset by peer > at sun.nio.ch.FileDispatcher.read0(Native Method) > at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:21) > at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:233) > at sun.nio.ch.IOUtil.read(IOUtil.java:206) > at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:207) > at > org.apache.catalina.cluster.tcp.TcpReplicationThread.drainChannel(TcpReplicationThread.java:123) > at > org.apache.catalina.cluster.tcp.TcpReplicationThread.run(TcpReplicationThread.java:67) > > and I also see this: > > SEVERE: TCP Worker thread in cluster caught 'java.io.IOException: Connection > reset by peer' closing channel > java.io.IOException: Connection reset by peer > at sun.nio.ch.FileDispatcher.read0(Native Method) > at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:21) > at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:233) > at sun.nio.ch.IOUtil.read(IOUtil.java:206) > at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:207) > at > org.apache.catalina.cluster.tcp.TcpReplicationThread.drainChannel(TcpReplicationThread.java:123) > at > org.apache.catalina.cluster.tcp.TcpReplicationThread.run(TcpReplicationThread.java:67) > at org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:296) > at org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:372) > at org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:694) > at > org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:626) > at org.apache.jk.common.SocketConnection.runIt(ChannelSocket.java:807) > at > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:644) > at java.lang.Thread.run(Thread.java:534) > > > Can I solve this by tweaking some timeouts? > I'm about to upgrade to 5.0.28 soon. Is this going to help? > > Ronald. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
