Received: from PACIFIC-CARRIER-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA21017; Mon, 5 Feb 96 03:37:17 EST Received: from liquor.cabi.net by MIT.EDU with SMTP id AA17772; Mon, 5 Feb 96 03:37:05 EST Received: by liquor.cabi.net (8.7.3/8.7.3) id DAA02069; Mon, 5 Feb 1996 03:37:23 -0500 Resent-Date: Mon, 5 Feb 1996 03:37:23 -0500 Message-Id: From: peter@vpro.nl (Peter Busser) Subject: Does Linux Java block? To: java-linux@java.blackdown.org Date: Mon, 5 Feb 1996 09:31:15 +0100 (MET) X-Mailer: ELM [version 2.4 PL25] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-Id: <"wdXzr.0.QS.e2S5n"@liquor> Resent-From: java-linux@java.blackdown.org X-Mailing-List: archive/latest/1045 X-Loop: java-linux@java.blackdown.org Precedence: list Resent-Sender: java-linux-request@java.blackdown.org Howdy! When I wrote a few small network servers in Java, I noticed that the Java runtime is always in a runnable state. On fast computers it is not so obvious, but on a 386DX40, with several sockets waiting for connection, it is. When I looked with strace it showed that the runtime polls the sockets continuously. This also happens when there is only one socket waiting. Is that because the Linux Java does not have kernel threads? Is there something to do about it (except implementing kernel threads)? Groetjes, Peter Busser -- UNIX sysadmin, database admin, TCP/IP netadmin, security specialist Tel.: +31-35-712709 I'm the operator with my pocket calculator... (t/m 31 maart, daarna niet meer)