From owner-freebsd-java Sun Apr 23 17:36:32 2000 Delivered-To: freebsd-java@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.79.126]) by hub.freebsd.org (Postfix) with ESMTP id 669C437B88B for ; Sun, 23 Apr 2000 17:36:28 -0700 (PDT) (envelope-from nate@yogotech.com) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.79.115]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id SAA00657; Sun, 23 Apr 2000 18:36:25 -0600 (MDT) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id SAA09319; Sun, 23 Apr 2000 18:36:25 -0600 (MDT) (envelope-from nate) Date: Sun, 23 Apr 2000 18:36:25 -0600 (MDT) Message-Id: <200004240036.SAA09319@nomad.yogotech.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Taso Lyristis Cc: freebsd-java@FreeBSD.ORG Subject: Re: Socket bug and workaround example for FreeBSD JDK 1.2.2 In-Reply-To: <39037F2B.8E010E21@lyrisoft.com> References: <39037F2B.8E010E21@lyrisoft.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > The quick description of this bug is the following: When implementing a > TCP/IP server, the native method java.net.SocketInputStream.socketRead() > throws a SocketException: Resource temporarily unavailable instead of > blocking until data becomes available. This breaks any Java code that > depends on a blocking read from a socket's input stream. Can you give more detailed instructions on how to reproduce the bug? Otherwise, I can assume that it works, since if I run the program no errors are produced. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message