Can't start the AWT because Java was started on the 1st thr

[jgp]

Hi,

I get:

Code: Select all

Designer [6.6.0.200802252258]: 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

Product: GWT Designer Evaluation
Version: 4.0.0.200802260007
Expected: Eclipse 3.3
Actual: Eclipse 3.3.100.v20070530
Actual Eclipse Build Name:
Actual Eclipse Build ID: M20071023-1652
IDE Actual Name: Eclipse
IDE Actual Version: 3.3.2.R33x_v20071022
IDE Actual NL: en_US
Activation Key: GWTDesignerEval-WK0SH-FM0UY-AZCWR
Physical Address: 00-1C-B3-FF-FE-A1-E3-F0, HardwareAddress[00-1B-63-35-3C-5E], HardwareAddress[00-1C-B3-BF-D3-33]
Code Gen: Flat Mode, Use Existing, First Assignment, Make Final
Events: Anonymous Class
GWT Home: /Users/jgp/Documents/Workspaces/marvin-3.3/com.google.gwt
Platform Product: Eclipse
Platform Version: 3.3.2.R33x_v20071022
OS Name: Mac OS X
OS Architecture: i386
OS Version: 10.5.2

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

Designer [6.6.0.200802252258]: 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

Product: GWT Designer Evaluation
Version: 4.0.0.200802260007
Expected: Eclipse 3.3
Actual: Eclipse 3.3.100.v20070530
Actual Eclipse Build Name:
Actual Eclipse Build ID: M20071023-1652
IDE Actual Name: Eclipse
IDE Actual Version: 3.3.2.R33x_v20071022
IDE Actual NL: en_US
Activation Key: GWTDesignerEval-WK0SH-FM0UY-AZCWR
Physical Address: 00-1C-B3-FF-FE-A1-E3-F0, HardwareAddress[00-1B-63-35-3C-5E], HardwareAddress[00-1C-B3-BF-D3-33]
Code Gen: Flat Mode, Use Existing, First Assignment, Make Final
Events: Anonymous Class
GWT Home: /Users/jgp/Documents/Workspaces/marvin-3.3/com.google.gwt
Platform Product: Eclipse
Platform Version: 3.3.2.R33x_v20071022
OS Name: Mac OS X
OS Architecture: i386
OS Version: 10.5.2

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


On my Mac. I am fairly new to Mac, but where should I change these settings?

Thanks...

[jgp]

Hmm, i was not very precise, this is when i start a new Project, just after the creation of the new Module.

[jgp]

A solution...

find eclipse.ini, remove --XstartOnFirstThread.

My current eclipse.ini is :

Code: Select all

-showsplash
org.eclipse.platform
-vmargs
-Xdock:icon=../Resources/Eclipse.icns
-XstartOnFirstThread
-Xms40m
-Xmx512m
-XX:MaxPermSize=256m
-Dosgi.requiredJavaVersion=1.5
-Dorg.eclipse.swt.internal.carbon.smallFonts

[Eric Clayberg]

The error you are seeing is a well known Eclipse problem with Leopard. It is definitley not a GWT Designer issue. Fortunately, that problem has been resolved in newer Eclipse builds.

As stated earlier in this forum, if you use Eclipse 3.4M4/M5 or any recent Eclipse 3.3.2 build, you should be OK. You don't want to be using Eclipse 3.3.1.x

[charles]

I've exactly the same problem.

I'm running Eclipse 3.3.2, GWT 1.4.61, the lastest GWT Designer build and Leopard.

I removed -XstartOnFirstThread from eclipse.ini as you suggested but the problem is still there.

I've never come across this problem until I install GWT Designer.

Are you sure that "It is definitley not a GWT Designer issue"?

Thanks.

Charles.

[Eric Clayberg]

Are you sure that "It is definitley not a GWT Designer issue"?

Yes. This is a well documented Eclipse issue that started happening once Leopard came out.

It is a caused by a low level Eclipse SWT/AWT conflict that Eclipse.org and Apple are still trying to resolve.

It seemed to have been fixed as of OSX 10.5.1, but teh problem seems to have come back as of OSX 10.5.2.

There is nothing that we can do to resolve it as it is not occurring in our code.

[charles]

Okay then.

So currently, there is no way to use GWT Designer on Leopard?

Cheers.

[peterblazejewicz]

hi Charles,
do three things:
#1
download Leopard GWT build:
http://code.google.com/support/bin/answ ... opic=13006
#2
download Eclipse Ganymede OSX release (that's Eclipse 3.5 current milestone, most stable thing I think I've used so far):
http://www.eclipse.org/downloads/downlo ... bon.tar.gz

#3
then use any of supported way to add GWTD into your eclipse (downloadable feature/plugins set or via update page),

I haven't touched anything, everything worked out of the box, I've only modified eclipse.ini to add some ram to jvm,

I'm on Leopard from two days and GWTD/Eclilpse/GWT was one of my priorities. They work pretty fast (everything takes seconds).

I'm using OSX 10.5.2/Java 1.5 (default leopard install) on intel/dual core machine,

regards,
Peter

[peterblazejewicz]

Are you sure that "It is definitley not a GWT Designer issue"?

Yes. This is a well documented Eclipse issue that started happening once Leopard came out.

It is a caused by a low level Eclipse SWT/AWT conflict that Eclipse.org and Apple are still trying to resolve.

It seemed to have been fixed as of OSX 10.5.1, but teh problem seems to have come back as of OSX 10.5.2.

There is nothing that we can do to resolve it as it is not occurring in our code.

Hi Eric,
I'm using latest GWTD build/Leopard 10.5.2/built-in Leopard Java 1.5 and have no issues really.
I'm using Ganymede Eclipse builds as I noticed on Windows they are pretty stable, fast and feature rich,

regards,
Peter

[Eric Clayberg]

So currently, there is no way to use GWT Designer on Leopard?

I didn't say that at all. GWT Designer works quite well on Leopard with the right combination of Eclipse, JDK and GWT.

We are using it on several Macs (including one running 10.5.2) without any problems. If it isn't working using Eclipse 3.3.2 for you (that combination does work for us), then try the latest Eclipse 3.4 build instead. Those work for us as well.

Eclipse.org is trying to keep ahead of the bugs that Apple introduces with each update, but it is a very fluid process. I spoke with members of the Eclipse SWT team last night at EclipseCon and they are very aware of (and frustrated by) the problems with OSX and are working to resolve them once and for all. Unfortunately, it is a slow process and currently exacerbated by the fact that their main contact and champion at Apple with these issues recently left Apple to work for a different company. Patches that Apple applied on their end have sometimes been left out of newer OSX builds and work arounds that Eclipse has put into place have intermittently failed in different OSX releases.

[charles]

Thanks Peter, I have followed your steps and that works fine now.

Cheers.

[Eric Clayberg]

Thanks Peter, I have followed your steps and that works fine now.

What was different vs. what you were doing earlier? Just the Eclipse version?

[charles]

Yes indeed, just the eclipse version (3.3.0)

[Eric Clayberg]

Yes indeed, just the eclipse version (3.3.0)

That would do it. When Apple released Leopard, it included several serious regressions in is support for SWT. Google had to patch GWT and Eclipse.org had to patch SWT to get both working again.