Ah, but there's a problem. The connection in question is going via localhost, and this is Ubuntu or MacOSX, so tcpdump won't see the packets. For Windows I'd have to install the Microsoft Loopback Adapter which brings its own set of problems. Darn.
Karl On Wed, Jan 23, 2013 at 6:47 AM, Karl Wright <[email protected]> wrote: > We've already looked at wire debugging. See CONNECTORS-616. But with > Wireshark it is true we could prove who is actually doing the close. > Good suggestion. > > Karl > > On Wed, Jan 23, 2013 at 6:05 AM, Asankha C. Perera <[email protected]> wrote: >> If this is not related to load, you could collect a sizable TCP / Wireshark >> dump to investigate why one party is closing its side of the TCP connection >> >> regards >> asankha >> >> >> On 01/22/2013 10:08 PM, Karl Wright wrote: >>> >>> This happens both under Tomcat and under Jetty. It happens sometimes >>> when only two documents are being indexed at the same time, so it is >>> not actually related to "load". It also seems to occur during >>> connection setup rather than when there are established connections. >>> >>> Karl >> >> >> -- >> Asankha C. Perera >> AdroitLogic, http://adroitlogic.org >> >> http://esbmagic.blogspot.com >> >> >> >> >> --------------------------------------------------------------------- >> 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]
