On Jul 27, 2005, at 4:01 PM, Elliotte Harold wrote:
2005-07-27 18:56:29.016 java[1245] Apple AWT Java VM was loaded on
first thread -- can't start AWT.
Exception in thread "main" java.lang.InternalError: Can't start the
AWT because Java was started on the first thread. Make sure
StartOnFirstThread is not specified in your application's
Info.plist or on the command line
This mean anything to anybody? Google finds quite a few scattered
hits on this, but none that clearly tell me how to solve the
problem. Looking them over this appears like it might be a known
Apple VM bug.
There is a well known issue with SWT and Swing. Basically, in order
to integrate with the OS event loop properly in OS X, SWT must be
started on the first thread in the application. I'm sure someone else
can explain the lower level OS specifics better than I can. Apple has
included a -XstartOnFirstThread VM option to enable SWT applications
to run properly on OS X.
Swing on the other hand integrates with the OS event loop in an
incompatible way. When you try to run both SWT and Swing components
in the same application, their event loops deadlock, hanging the
application.
Scroll down for the informative posts from Andre Weinand.
--
Peter Molettiere
Founder, Green Array
_______________________________________________
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
