What is alarming is that
MRJ 2.2 seems to allow two of these runnables to execute at once,
from different threads,
which leads to the deadlock we are seeing.
Have you tried using the MRJ dcmd with MacsBug, dropping into the
debug monitor and see if that tells you anything useful? There were
one or two things pertinent to stack crawls and monitor locks as I
remember. There was a pertinent Tech Note quite a while back, on
MacsBug and MRJ with info on the dcmd. The classic version of my
application used to support using it directly from a running java
application. That was based on some code from JShell.
MRJ was timesliced threading about the only other thing I'm
remembering that might apply.
I used the MRJ DCMD to produce the stack traces I posted. It
also showed my which monitors were held by the threads, and
that let me determine that AWT-Dispatch-Proxy was waiting on
a monitor held by AWT-EventQueue-0. I will try and find that
tech note and re-read it, its been a while. Thanks for the
reminder that it exists.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
