After upgrading to Java 1.6.0_14, a GWT application in Eclipse no longer stops at breakpoints even though Eclipse shows that the breakpoints are active. Are there workarounds for this issue?
+2
A:
This is a known issue with GWT and Eclipse. The current recommended workaround is to use Java 1.6.0_13 for debugging.
Greg Bacon
2009-06-20 16:55:51
I experienced this with Java 7 b59 too. Annoying.
kd304
2009-06-22 13:06:54
+2
A:
The error occurs commonly with JDK 1.6.0_14 and is probably not related to GWT. Swing apps also have faced similar issues before. Here are some relevant links:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=279137
Thimmayya
2009-06-23 17:18:27
Fron that Eclipse bug, it seems a workaround inside 6u14 is to use the JVM option: -XX:+UseParallelGC
gojomo
2009-07-24 21:07:22
+2
A:
The JDK early release 6u18 fixes this issue - finally! http://bit.ly/34aUZB
jah
2009-08-21 23:22:01
A:
We upgraded to GWT 2.0 and now our client-side breakpoints no longer work. Server break points work. We've tried all the suggested JDKs,13,16, 20, no love. It must be something in our project, because other projects break fine. Burned a day on this already.
mike
2010-05-03 13:47:08