[john m. o’neill]

Hi:

I have been running MyEclipse for about a year now. I had previsouly been running under Eclipse 2 and have successfully developed several applications. I recently upgraded to Eclipse 3 and the latest version of MyEclipse. Now all of the sudden when I try to run J2EE apps in the debugger, which have been developed and deployed for months, I am hitting breakpoints in system libraries. I am breaking on BASE64Decoder.class, and URLClassPath$JarLoader.class among others. I have to hit the “Resume” icon about 10 times before it gets back into my application code.

For my upgrade I had performed an uninstall on MyEclipse 2.x prior to upgrading/re-installing Eclipse and then MyEclipse. I have not changed the J2EE jars, or my local project jars.

Any help would be greatly appreciated.

Thanks,

John

[Scott Anderson]

John,

I haven’t seen this issue personally. It might be a preference migration problem in your workspace when going from Eclipse 2.0 to 3.0. I’d try to open the Breakpoints View, select them all, and delete them. Also, check the debug settings at Window > Preferences > Java > Debug. Also make sure you don’t have any exception breakpoints set as several libs throw and catch exceptions and this can certainly trigger breakpoints. Finally, try lauching the server with all breakpoints disabled, using the button in the toolbar of the breakpoints view. Does this change the behavior? Oh, and what JDK are you using?

[john m. o’neill]

Hi Scott:

I went into the Breakpoint view and removed my one application level breakpoint. I verified that I had no Java Exception breakpoints set, either caught or uncaught. I then ran my application in the debugger and it worked fine! I then set an application level breakpoint and ran the application through the debugger…it still works!!

Thanks for your helpful suggestions,

John

[Scott Anderson]

John,

No problem. I’ve been bitten by the “phantom breakpoint” more than once myself. Glad it worked for you too.

[Author]

Posts