Eclipse StartOnFirstThread Error (and fix!)

This appears to be an issue with the JVM under Leopard (Mac OS X 10.5), but I started getting the following error within Eclipse when using the ResourceBundleEditor plugin:

StartOnFirstThread Error Message

It also apparently happens with other plugins/apps and is an issue with the AWT kit in the new JVM. After pouring through all of my Eclipse config files and determining that I definitely was NOT specifying StartOnFirstThread anywhere, I found this fix:

Within the Eclipse application bundle, in the file Contents/MacOS/eclipse.ini, add this line:

-Djava.awt.headless=true

Save the file, and restart Eclipse. Problem solved.

Posted

January 24, 2008

Apple, Java

Devon

Tags:

eclipse, mac, os x

Comments

4 responses to “Eclipse StartOnFirstThread Error (and fix!)”

Adam Fisk

February 16, 2008

Thanks a million – worked like a charm. I just had one of those days almost completely consumed with Eclipse/webapp/maven etc configuration issues, so it was very helpful to knock this particularly annoying one off at the end. Much appreciated.

-Adam

Reply
Devon

February 16, 2008

Adam:

I’m very glad I could help!

Devon

Reply
Greg Johnson

February 17, 2008

Alas, this is a big pain for me with my RCP app which only works when run from within Eclipse, but not once exported. Just in case someone else comes looking, this doesn’t help me. I’m using the SWT_AWT bridge, and (makes sense really) headless AWT doesn’t make anything better. Back to google…

But thanks – you got me excited for 18seconds!

Reply
Devon

February 17, 2008

Greg:

I’m sorry to disappoint! If you find a solution, it would be great if you could share it here as well for other people like yourself.

Good luck!

Devon

Reply

Eclipse StartOnFirstThread Error (and fix!)

Comments

4 responses to “Eclipse StartOnFirstThread Error (and fix!)”

Leave a Reply Cancel reply