[Neil Croll]

Hi,

We are experiencing issues with the speed of debugging, when executing WebLogic 8.1 from within MyEclipse.

The issues are that stepping through code can take up to 10 seconds to just go from one simple statement to another.

When debugging on weblogic, when it is not running within MyEclipse is lightening fast – even when debugging on a remote server.

Can you shed any light on this?
I don’t recall this being an issue in the previous beta 3.8 release.

We are using Eclipse 3.0.0, MyEclipse 3.8GA. Our machines are P4 2.4GHz, 1Gb RAM.

Thanks,

[Riyad Kalla]

Under Window > Preferences > Java > Debug, have you tried unchecking “suspend execution on breakpoint” and see if that helps performance?

[Neil Croll]

This did not appear to have any effect.
I should have previously stated that the first time a debug session is started within eclipse, the session is fast. However, the second time the debugger reaches the breakpoint, it’s painfully slow, taking nearly 10secs to from “int num = 0;” to “num++;” (for example)

[Riyad Kalla]

Are you starting WebLogic with good ms/mx params to give it plenty (512) mb of memory?

[Neil Croll]

Ok, I tried adding the ms/mx params, but it appeared to make no difference.

I tried:

-Xms128m -Xmx512m
-Xms128m -Xmx1024m
-Xms128m -Xmx2048m

I added this to the Optional Java VM arguments section of the WLS8.1 JDK tree, under MyEclipse.

I even tried adding them to the Eclipse startup command line, but with even less success than in the above location.

[Scott Anderson]

crollster,

For 3.8.2 we’ll be profiling MyEclipse to look at resource utilization and timing. We’ve got an open problem report on this that we’ll be looking at as part of that effort. Also, if you haven’t already, I’d highly recommend that you update to verion 3.8.1 as it included several fixes to reported issues. However, I don’t know if any of them would’ve had an impact on this issue.

Can you also provide the approximate size / makeup of your application? For example, is it a full 3-tier app in an EAR, or a a web application in a WAR? Are you using packaged or exploded deployment? Have you tried the other? Does that have an effect? How many projects are open in your workspace? If you temporarily close the projects you’re not using, does this have an effect on the debug speed? Have you noticed the stepping being slow in JSP’s only or in JSP’s and Java files or just Java files? Answers to all of these will help us isolate the problem much more quickly, so thanks in advance for providing them.

[Neil Croll]

Scott,

Thanks for your response. The issue is now resolved. :o)

I previously had 7 projects open within the workspace (including one project which was a dependency on the debugged project). Closing this dependant project allowed the debugger to regain its former lightening speed.

For your reference:

* Project is a simple JSP/JavaBeans/Servlets/DAOs, Model 1/Model 2 mix, deployed as WAR file. (no EJBs)
* The WAR file is only 2.11Mb in size.
* We are running v3.8.1
* The debugging was slow in Java files – i haven’t tried JSP debugging in 3.8.x yet.
* the -Xms and -Xmx parameters were not required in this instance.

[Scott Anderson]

Ah, good to hear! Thanks for the folllowup.

[Author]

Posts