I've a little cluster with 2 Tomcats 5.5.12 and 1 apache2.2 running on fedora 4.0 linux box. (tomcat and apache are connected by mod_jk.so module) During tests I have found that exception while I startup on this cluster. -------------------------------------------------------------------------------- --- WARNING: Manager [], requesting session state from org.apache.catalina.cluster.mcast.McastMember[tcp://10.10.10.2:4003,catalina ,10.10.10.2,4003, alive=61880]. This operation will timeout if no session state has been received within 60 seconds. Feb 26, 2006 6:51:32 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:125) at org.apache.catalina.cluster.tcp.TcpReplicationThread.run (TcpReplicationThread.java:69) Feb 26, 2006 6:52:31 PM org.apache.catalina.cluster.session.DeltaManager waitForSendAllSessions SEVERE: Manager []: No session state send at 2/26/06 6:51 PM received, timing out after 60,086 ms. Feb 26, 2006 6:52:32 PM org.apache.catalina.cluster.session.DeltaManager getAllClusterSessions WARNING: Manager []: Drop message SESSION-GET-ALL inside GET_ALL_SESSIONS sync phase start date 2/26/06 6:51 PM message date 2/26/06 6:51 PM INFO [main] - Tiles definition factory loaded for module ''. -------------------------------------------------------------------------------- ------ Is that a known bug? Has anyone fixed this problem in an offical patch?
It is not an error to worry about. It is an incorrectly reported warning. The sender TomcatA will periodically close its connections, and TomcatB reports this as an error. Nothing to worry about, and in Tomcat 5.5.16 this has been fixed to only report a 1 line warning.