[Gilles Brisson]

Hi Riyad,

Here are my answers…

Do you consistently get the source not found issue with all code, or only JSPs?

Typically, most debugging is done against Java code, although on occasion we also debug JavaScript and JSP.

Does it happen every time with every project, or just sometimes with some projects?

We have a solution distributed across 4 layers, with approximately 25 components in as many projects. The project (or type of project) does not seem to make any difference.

Also what did you mean by “lack of refresh is VERY frequent”?

As an example, the executing code would stop on a breakpoint. The Java source file would be displayed properly with the proper line of code highlighted. Then as we step, at some point, the “step-over” arrow would be disabled but the “resume” arrow would still be active. Then clicking the “resume” arrow would get to the next breakpoint in the source code, but the “debug” panel would still show the information of the previous breakpoint. Sometime, it seems that “debug” panel will refresh properly after a long while (10-20 seconds); sometime clicking inside the “debug” panel seems to trigger a refresh, sometimes nothing happens for a long while… It is hard to describe, as it does not seem to be consistent.

One note, debugging Applet does not seems to be as problematic and the stepping of the code is faster; but I have not acquire any specific metrics.

And with regard to the lost debugging sessions, do you have any anti-virus or anti-spyware software running on your machines that are dropping debugging sessions?

We do use anti-virus (but not anti-spyware), exactly as we did with MyEclipse V4. Still have the same behavior even after disabling it.

Are these debugging sessions very long, or short?

Typically, on average, a debugging session is approximately 15-20 minutes. After which we typically, make some changes, stop the server, redeploy, start the server, and finally test again.

Hope that helps,
Gilles Brisson
CTO, Entiera

[Riyad Kalla]

I’m going to file an issue to investigate this. There are a whole slew of bug fixes planned for the 5.0.3 release and we have had reports of the “refresh” issue of the debugger display and are looking into that. We’ve had one other user report the dropped debug sessions but weren’t able to get a reproducable test case which makes a real nightmare for our developers to try and debug.

When 5.0.3 is release (Nov 6th is our target, might go longer depending on testing required, but probably only a few days), please keep me posted on the situation of the team. If things improve or get worse.

[Author]

Posts