I'm using Eclipse 4.19.0 with quite a large java-ear-project including about 20 subprojects.

When debugging, eclipse doesn't jump to the line of code immediately on a breakpoint. It doesn't hang. I can step through the code and the variables are shown but the current line isn't linked with the editor.

Then, after some minutes, it suddenly jumps to the right line. From now on, it jumps to the line immediately on breakpoints.

So the problem is: it does jump to the line of code, but for the first time it takes minutes to do so.

After restarting the server (Oracle Weblogic 12), the behaviour repeats.

In this post a very similar problem is described and visualized with an animated gif. But no solution provided.

Is there anything I can do to get eclipse linking to the editor immediately on a breakpoint?

CodePudding user response：

The problem has been a huge number of external libraries in the Source Lookup Path. We're using gradle. I guess when gradle configures the eclipse project it adds all referenced libs to the lookup path.

Solution is to remove everything from Source Lookup Path and then simply add all subprojects. Now the debugger behaves as expected.

Drawback of this solution is that the debugger cannot step into external libs until you add them one by one to the lookup path.