AppContext issue in Apple Java 6 -- same issue in Oracle Java 7?

[Michael Hall]

On Jun 26, 2013, at 5:46 PM, Doug Zwick wrote:

> I have dug deeper into this, and we are somehow getting our code running on AWT-EventQueue-0 in the "main" ThreadGroup, and not on AWT-EventQueue-2 in the "javawsApplicationThreadGroup" group

This is normal for applications, if not jws, maybe jws is running more like platform app's now?
From my HalfPipe app.

dojava
javax.swing.SwingUtilities.invokeLater(new Runnable() { public void run() { System.out.println(Thread.currentThread() + " " + javax.swing.SwingUtilities.isEventDispatchThread()); }});
Thread[AWT-EventQueue-0,6,main] true
dojava: done

Although I was sort of remembering the AppKit thread being the actual EDT? Must be a misremember there.
You aren't showing a deadlock. I think actual instances of stack crawls showing deadlock would be more useful to go on if theres a problem.
As I remember there have been multiple AWT-EventQueue-# threads going back a long time, these haven't been a deadlock problem previously that I remember.
Thread group I'm not sure how would apply?

Michael Hall

trz nio.2 for OS X http://www195.pair.com/mik3hall/index.html#trz

HalfPipe Java 6/7 shell app http://www195.pair.com/mik3hall/index.html#halfpipe

AppConverter convert Apple jvm to openjdk apps http://www195.pair.com/mik3hall/index.html#appconverter