Date: Wed, 29 Jul 2009 08:19:49 -0700 From: "Peter Steele" <psteele@webmail.maxiscale.com> To: <freebsd-questions@freebsd.org> Subject: Diablo JDK threads implementation Message-ID: <B8A480488C0C6849826655761349EA431F6F43@owa.webmail.maxiscale.com>
next in thread | raw e-mail | index | archive | help
We've developed a server platform around FreeBSD 7.0 consisting of several applications written in C and one primary application written in Java (JDK 1.6). We're seeing cases in some of ouor stress tests where some threads in our JAVA application appear to get no CPU time for extended periods of time (sometimes over a minute), even though the box has lots of idle time available and all of the C threads are running without a glitch. We thought originally it might be memory related and the GC was kicking in and freezing the JDK. That's not the case though, and in fact the memory footprint of the Java application is very small.=20 =20 I know I've read that some ports of Java do not always use native threads for the JDK thread model. Does anyone know the story with the Diablo JDK port? Is there another explanation what might be causing this problem? =20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B8A480488C0C6849826655761349EA431F6F43>