Date: Mon, 27 May 2002 09:26:38 +0300 From: Ari Suutari <ari.suutari@syncrontech.com> To: Greg Lewis <glewis@eyesbeyond.com>, "Robert F. Ross" <rross@recourse.com> Cc: freebsd-java@FreeBSD.ORG Subject: Re: JDK 1.3.1, FreeBSD 4.5, JNI and select() Message-ID: <200205270926.39005.ari.suutari@syncrontech.com> In-Reply-To: <20020527012831.A99647@misty.eyesbeyond.com> References: <Pine.GSO.4.21.0205241256290.1002-100000@recourse.com> <20020527012831.A99647@misty.eyesbeyond.com>
index | next in thread | previous in thread | raw e-mail
Hi, On Sunday 26 May 2002 18:58, Greg Lewis wrote: > > > An ldd on the final java binary > > shows that it's using libc.so.4, not libc_r.so.4. I've been experiencing > > problems with select() calls in JNI routines always waiting for the full > > timeout when checking readfds (write seems happy) instead of returning as > > soon as the data is available. poll() appears to have the same > > behavior. Has anyone seen this issue and know how to fix it? > > Not having tried to do this I haven't seen this issue. The Java Comm API > uses this select() in JNI code and seems to work ok, however I'm not > sure of the details. It might be worth looking at the code for it > (its in the PR system to be committed as a port if it hasn't been > already). Java Comm API used select in jdk 1.1.8 days, but I have changed it to use poll because of similar problems. If I remember correctly, there are wrappers in green_threads package for various syscalls. There is a wrapper for "poll", but there is no wrapper for "select" which breaks threading when it is called by JNI code. Ari S. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the messagehelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200205270926.39005.ari.suutari>