GRECLIPSE
  1. GRECLIPSE
  2. GRECLIPSE-1208

JDI Event Dispatch error when trying to step into or over code in groovy classes

    Details

    • Type: Bug Bug
    • Status: Resolved Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 2.5.2.Release
    • Fix Version/s: 2.5.2.Release
    • Labels:
    • Environment:
      Fedora 15 x86_64, Eclipse 3.6.2 for Linux GTK x86_64, Groovy-Eclipse Feature 2.5.2.xx-20110921-1500-e36
    • Number of attachments :
      0

      Description

      I completely re-installed Eclipse 3.6.2 together with the SpringSource STS plugins over the weekend and tried debugging an existing workspace of mine which I created earlier in the month.

      For some reason I get the following error as per the eclipse workspace .metadata/.log file whenever I try and step over or into any groovy classes/code lines.

      !ENTRY org.eclipse.core.jobs 4 2 2011-09-26 10:04:59.659
      !MESSAGE An internal error occurred during: "JDI Event Dispatch".
      !STACK 0
      java.lang.AbstractMethodError: com.springsource.sts.groovy.debug.core.GroovyDebugProvider.isAlwaysInteretingLaunch()Z
      at org.eclipse.contribution.jdt.debug.DebugHooksAspect.isInterestingLaunch(DebugHooksAspect.aj:253)
      at org.eclipse.contribution.jdt.debug.DebugHooksAspect.ajc$inlineAccessMethod$org_eclipse_contribution_jdt_debug_DebugHooksAspect$org_eclipse_contribution_jdt_debug_DebugHooksAspect$isInterestingLaunch(DebugHooksAspect.aj:1)
      at org.eclipse.jdt.internal.debug.core.model.JDIThread$StepHandler.locationShouldBeFiltered_aroundBody1$advice(JDIThread.java:81)
      at org.eclipse.jdt.internal.debug.core.model.JDIThread$StepHandler.locationShouldBeFiltered(JDIThread.java:1)
      at org.eclipse.jdt.internal.debug.core.model.JDIThread$StepHandler.handleEvent(JDIThread.java:2168)
      at org.eclipse.jdt.internal.debug.core.EventDispatcher.dispatch(EventDispatcher.java:155)
      at org.eclipse.jdt.internal.debug.core.EventDispatcher.access$0(EventDispatcher.java:104)
      at org.eclipse.jdt.internal.debug.core.EventDispatcher$1.run(EventDispatcher.java:250)
      at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

      My current Groovy-Eclipse Feature is 2.5.2.xx-20110921-1500-e36. Yes that is correct. Strange 2.5.2 is only due for relase this Friday so not sure why my Eclipse managed to pull a version of it already.

      When I originally installed Eclipse 3.6.2 and STS at the beginning of the month everything (including debugging) worked flawlessly. So something must have broken during this month.

      This is a critical error as I cannot debug any code anymore as this error comes up when you hit your first breakpoint and try to step from there.

        Activity

        Hide
        Zahir Toufie added a comment -

        The 2.8.0.M2 update seems to have fixed the problem on my test Eclipse environment.

        Let me try it on my main Eclipse environment and see if I can debug my Grails projects again.

        Show
        Zahir Toufie added a comment - The 2.8.0.M2 update seems to have fixed the problem on my test Eclipse environment. Let me try it on my main Eclipse environment and see if I can debug my Grails projects again.
        Hide
        Andrew Eisenberg added a comment -

        The reason why you were getting that problem for trying to install on e37 is that you were installing on top of Eclipse 3.7.1. Until Friday, Groovy-Eclipse did not install onto 3.7.1. It looks like you tried to install a Groovy-Eclipse snapshot that was release on Wednesday.

        Apologies for all of your installation and compatibility woes. You just happened to try to reinstall during a bad window. Since Groovy-Eclipse provides a patch for JDT core (to integrate groovy into the Java compiler), we cannot release our patch targeting a new release of Eclipse until that release has been made official.

        Please let me know if you have any more problems.

        Show
        Andrew Eisenberg added a comment - The reason why you were getting that problem for trying to install on e37 is that you were installing on top of Eclipse 3.7.1. Until Friday, Groovy-Eclipse did not install onto 3.7.1. It looks like you tried to install a Groovy-Eclipse snapshot that was release on Wednesday. Apologies for all of your installation and compatibility woes. You just happened to try to reinstall during a bad window. Since Groovy-Eclipse provides a patch for JDT core (to integrate groovy into the Java compiler), we cannot release our patch targeting a new release of Eclipse until that release has been made official. Please let me know if you have any more problems.
        Hide
        Zahir Toufie added a comment -

        If I tried to upgrade to 3.7.1 today, will I pick up the usable Groovy-Eclipse release?

        i.e. Has the correct Groovy-Eclipse bits for 3.7.1 been released and will STS automatically find it now?

        LOL, serves me right for living on the cutting edge, but hey that's a developers life.

        Show
        Zahir Toufie added a comment - If I tried to upgrade to 3.7.1 today, will I pick up the usable Groovy-Eclipse release? i.e. Has the correct Groovy-Eclipse bits for 3.7.1 been released and will STS automatically find it now? LOL, serves me right for living on the cutting edge, but hey that's a developers life.
        Hide
        Zahir Toufie added a comment -

        OK, the 2.8.0.M2 build fixed the JDI Event Dispatch problem on Eclipse 3.6.2.

        Thanks for all the help and I'll be sure to try Eclipse 3.7.1 again tonight.

        Show
        Zahir Toufie added a comment - OK, the 2.8.0.M2 build fixed the JDI Event Dispatch problem on Eclipse 3.6.2. Thanks for all the help and I'll be sure to try Eclipse 3.7.1 again tonight.
        Hide
        Zahir Toufie added a comment -

        STS 2.8.0.M2 fixes this issue

        Show
        Zahir Toufie added a comment - STS 2.8.0.M2 fixes this issue

          People

          • Assignee:
            Unassigned
            Reporter:
            Zahir Toufie
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: