GWT-Designer lockups

[wgdenge]

I run ECLIPSE 3.5 at work. I just installed the latest WindowBuilderPRO. I have also just started messing with GWT.

For the life of me I cannot get it to run in any stable form at all. I create a GWT-Designer project (tutorial) and only get a few steps. Seems that after I do the CSS portion of tutorial the designer locks up. If I restart eclipse, and click the design tab, it gets about 1/4 way thru initializing, then just hangs.

I came home today, and installed RH5.2 on my home PC to see if it would work if I used the Eclipse "Install software/Updates" feature.

I downloaded the latest Eclipse, then had it install WindowBuilderPro. Same thing.

Is there any LOG that I could look at to dump here to get some help? As I see it now GWT-Designer is a no-go.


Please, any help would be appreciated.

Wayne Dengel

[wgdenge]

Forgot to add, I am using Java-6u15, and Eclipse 'ee' version

[Eric Clayberg]

If you are using Linux, make sure that you are using the Sun JVM (not the one that came with your Linux distro) and that you review the following forum entry:

viewtopic.php?f=11&t=2082

The standard Eclipse ".log" file might show something.

[wgdenge]

Yes, it is standard SUN JVM jdk1.6.0_15jdk1.6.0_15

In the AM I will clean the LOG file, do a clean install, and dump the log here.
I assume you mean the <workspace>/.metadata/.log file?


wayne

[Eric Clayberg]

Also make sure that you are using xulrunner 1.9

[wgdenge]

Is there an easy way to get XULRUNNER, and have eclipse use that one instead of the system default.
OR
Is there an easy RPM that I could use.

I do not want to have to rebuild/link everything on my install that uses XULRUNNER


wayne

[Alexander.Mitin]

1. xulrunner can be downloaded from mozilla's site: http://releases.mozilla.org/pub/mozilla ... /releases/
Just unpack it into any place you like and run the eclipse against it as shown at link given by Eric above.
2. Yes, send <workspace>/.metadata/.log file and <project>/.gwt-logs/* files as well.
3. Run the eclipse from a terminal, then when it hangs, do 'kill -3 eclipse_pid_here' command from another terminal. This will produce the java threads dump on the first terminal, please send such dump.

[wgdenge]

So, I got everything work well on my home PC, turns out if I use RH5.3 all works fine.
I returned to work, and installed 5.3 on my workstation, and it has same old problems.

Only difference is home PC is single processor, work is DUAL processor.

Anyway in LINUX to force a process to run on one processor?

Looking at the dump done with kill -3 PID, it shows many threads in a WAIT state. Any issues with GWT designer on multiple processors?



wayne

[wgdenge]

Well, on RedHat 5.3 with latest XULRUNNER, and all new code it still locks up.
I can start a GWT project, and if I add a few things to the canvas, then exit, and re-enter DESIGNER, it locks.
Doing a dump here is what I get. (Only a few lines, this is from a printed copy)
Note: at this point, Eclipse is using 100% CPU)

Full thread dump Java HotSpot Client VM (11.0.b16 mixed mode, sharing);

"[ThreadPool Manager] - Idle Thread" deamon prio=10 tid=0x09660c00 nid=0x2709 in Object Wait()
[0x013da000..0x013db130]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
- waiting on <0x647365db8> a org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor)
at java.lang.Object.wait(Object.java:485)
at org.eclipse.equinox.internal.util.impl.tpt.threadpool.Executor.run(Executor.java:106)
-locked<0x647365d8> (a org.eclipse.equinox.internal.util.impl.tpt.threadpool.executor)

bla bla bla..

"CodePro backgorund Startup" prio=10 tid=0x920c000 nid=026f0 in Object.wait() [0x08c80000..0x08c81130]
java.lang.Thread.State: WAITING(on object monitor)
at java.lang.Object.wait(Native Method)
-waiting on <0x685a1668> (a java.util.ArrayList) at java.lang.object.wait(Object.java:485)
at com.instantiations.eclipse.startuo.StartupManager.start0(Startupmanager.java:207)
- locked <0x685a1668> (a java.util.ArrayList)
at com.instantiations.eclipse.startup.StartupManager.access$0(StartupManager.java:99)
at com.instantiations.eclipse.startup.StartupManager$1.run(StartupManager.java:87)

bla bla bla


Amazing thing is that Eclipse works fine, except when I start using GWT Designer.
What is wrong here???

[Alexander.Mitin]

Please zip up and attach here the full dump.

[wgdenge]

Sorry, I cannot do that. How about printing the dumps, and email you a SCAN?

wayne

[Eric Clayberg]

How about print, scan and OCR?

As long as we can see the complete dump, I guess it doesn't matter what the format is (just ZIP it if it is a large image).

[Alexander.Mitin]

try this:

Code: Select all

./eclipse >~/threads_dump.txt 2>&1

This means that all stdout and stderr data would be redirected and stored in 'threads_dump.txt' file in your home dir. So, invoking 'kill -3 ...' from another terminal will dump threads into this file.