Date: Thu, 19 Oct 2006 16:29:13 -0700 From: Greg Lewis <glewis@eyesbeyond.com> To: Joseph Gleason <fireduck@gmail.com> Cc: freebsd-java@FreeBSD.org Subject: Re: Bug in java.net.Socket close() behavior? Message-ID: <20061019232913.GB12461@misty.eyesbeyond.com> In-Reply-To: <7956f3200610161024o3598e217oba81116bd84a7c99@mail.gmail.com> References: <7956f3200610161024o3598e217oba81116bd84a7c99@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Oct 16, 2006 at 01:24:08PM -0400, Joseph Gleason wrote: > According to the API for java.net.Socket close(): > > "Any thread currently blocked in an I/O operation upon this socket > will throw a SocketException." > > http://java.sun.com/j2se/1.5.0/docs/api/java/net/Socket.html#close() > > I have observed that java 1.5 on FreeBSD does not follow this while > the Windows and Linux ones I have tested do. On the FreeBSD runtimes > that I have tested, a thread blocked on reading a socket just hangs > forever if the socket is closed. See http://www.freebsd.org/cgi/query-pr.cgi?pr=97921 -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : glewis@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061019232913.GB12461>