On 11/8/05, Oded Arbel <[EMAIL PROTECTED]> wrote:
> Java program was supposed to do was call wait() (a Java thread
> synchronization call) every second, which was indeed verified by
> stracing the Java process, and here is the output:
>
> futex(0x4d907b60, FUTEX_WAIT, 233, {0, 265545000}) = -1 ETIMEDOUT
> (Connection timed out)
> futex(0x805d33c, FUTEX_WAKE, 1) = 0
> gettimeofday({1131445296, 417683}, NULL) = 0
> clock_gettime(0, {1131445296, 417799000}) = 0
> futex(0x4d907b60, FUTEX_WAIT, 234, {0, 499884000}) = -1 ETIMEDOUT
> I suspect the futex() calls from the above trace - AFAIK they stand for
> "fast use mutex", but I don't understand enough about them to guess as
> to why it behaves that way.
Do you know if this is a "green-threads" or "linux-threads" JVM?
What does "java -version" give you?
Can you determine whether the Java process has multiple kernel-level threads?
Also if possible I think you would get beter results in general from
Java 5 (FKA 1.5).
(I personally installed BEA's JRockit JVM, which is supposed to be geared
towards high-performance servers).
--Amos
--
"We wanted proper outback: a place where men were men
and sheep were nervous." - Bill Bryson, "Down Under"
================================================================To unsubscribe,
send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
