ok, it looks like you might have ended up with a rogue socket,
and what happens is that any message sent to that socket just gets lost
in the ether, since it doesn't have any interest ops.
There is a workaround for this, turn off keep alives all together, or
implement a keep alive timeout
Opti
Hi all, I'm Raúl.
We had a tomcat 5.0.28 server configured with 2 clustered instances(working
perfectly), and we decided to migrate to java6 and the new tomcat 6.0.14.
We modify the configuration files to match the new tomcat 6.0.14 structure.
But now we have really annoying problems with the clu