Diablo JDK threads implementation
Ggatten at waddell.com
Wed Jul 29 15:33:56 UTC 2009
For fun you could try mapping to a different thread library with
From: owner-freebsd-questions at freebsd.org
[mailto:owner-freebsd-questions at freebsd.org] On Behalf Of Peter Steele
Sent: Wednesday, July 29, 2009 10:20 AM
To: freebsd-questions at freebsd.org
Subject: Diablo JDK threads implementation
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.
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
freebsd-questions at freebsd.org mailing list
To unsubscribe, send any mail to
"freebsd-questions-unsubscribe at freebsd.org"
<div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in'>
"This email is intended to be reviewed by only the intended recipient
and may contain information that is privileged and/or confidential.
If you are not the intended recipient, you are hereby notified that
any review, use, dissemination, disclosure or copying of this email
and its attachments, if any, is strictly prohibited. If you have
received this email in error, please immediately notify the sender by
return email and delete this email from your system."
More information about the freebsd-questions