Date: Thu, 29 Oct 1998 10:05:35 -0700 From: Nate Williams <nate@mt.sri.com> To: Mahadevan Iyer <iyer@internetdevices.com> Cc: java-port@FreeBSD.ORG, freebsd-java@FreeBSD.ORG, saurabh@internetdevices.com, namit@internetdevices.com Subject: Re: Possible Bug in JVM socket code on FreeBSD, java.net.Socket Message-ID: <199810291705.KAA16987@mt.sri.com> In-Reply-To: <36381ADB.DCCDAB3D@internetdevices.com> References: <36381ADB.DCCDAB3D@internetdevices.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> I have a simple Server and Client pair > Server listens for connections on fixed port > Clients connect to the server on the port > > The Client opens N connections to the server and keeps them open > The Server sends data on each of these connections > The Client listens for data on each of these connections in a single > thread > > N > 250 causes the Client to dump core I can verify that this bug does indeed exist in the FreeBSD JDK. However, I do not (yet) have any idea why. It's happening inside the OS dependant socket code, but I haven't yet figured out why. *IF* I run the program with 'java_g -t' (tracing), it works with more connections, but that changes the timing quite a bit (it's ALOT slower) and can possibly be using different compiler optimization which might cause the program to act differently. I'll keep looking into it, since this behavior is critical to the success of my product. Ahh, I just tested with a larger value, and it blows up. Unfortunately, it doesn't tell me why it's dying, since it appears that it might be dying in the call itself. :( More later. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810291705.KAA16987>