Submit it as a bug and/or send us the short example, it could very well be
another linuxthreads bug that we will have to work around or someone has
already discovered.
Java is one of the best stress tests of the linux threads library :*)
regards
calvin
>
>I've been unable to get blackdown native-thread VM implementation to
>work properly on my x86-based SMP machine. I'd be interested in
>corresponding with anyone who's had better luck.
>
>Essentially the problem is that code like:
> synchronized (lock) {
> lock.wait();
> }
>results in exceptions like:
> java.lang.IllegalMonitorStateException: current thread not owner
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java, Compiled Code)
> ...
>
>I see it happening in my code, in jdk code (e.g. rmiregistry) and in
>third-party code. I have a short example which makes the bogon
>trivially reproducable.
>
>I haven't had any problems on single-cpu machines, though I run a
>different kernel on those machines.
>
>I'm mostly using Blackdown 1.2.2RC4 with javacomp (though jit doesn't
>seem to matter). IBM JDK1.3 beta exhibits almost identical behavior.
>The "Sun" 1.3 beta with hotspot actually doesn't throw these
>exceptions - it silently hangs instead.
>
>BTW - I'm using a 2-cpu intel machine w/ various late-2.3-series
>kernels and glibc 2.1.3.
>
>Should I just give up on SMP+Java for the foreseeable future or what?
>
>thanks,
> -mik
>--
>Michael Thome ([EMAIL PROTECTED])
>
>
>----------------------------------------------------------------------
>To UNSUBSCRIBE, email to [EMAIL PROTECTED]
>with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
>
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
