[myoungstrom]

For some strange reason after upgrading to 3.1 and MyEclipse 4.0M2 occationally my webapp I’m developing begins to get really slow. Here is the strange thing, when I notice my server is going slow I look at my Task Manager and see my JBoss server instance and my Eclipse instance. I load a webpage my Eclipse instance suddenly maxes out CPU utilization when it should only be the JBoss server instance. After a while the page finally loads.

I don’t have any breakpoints set.

I was previously using Eclipse 3.1 M6 or 7 with 3.8.4 and never had this problem.

It doesn’t happen all the time it is fairly random. When I have the problem I have to restart eclipse and my JBoss instance then everything seems to work ok for a while again.

Any ideas? Do you think this is something that was broken in Eclipse between M7 and 3.1 final? Or do you think it is something wrong with MyEclipse?

Mike

[Scott Anderson]

Mike,

It might be that you’re not running either Eclipse or JBoss with enough RAM so that at some point it has to swap drastically to continue operation. Possible?

[myoungstrom]

I run JBoss with vm args -XX:MaxPermSize=128m -Xmx256M should be plenty. It was before with M7 and 3.8.4. Again when I have this problem the strange thing is that when I load the webpage in my browser my Eclipse java VM is where all the CPU load goes to not my JBoss VM. Even though I’m not doing anything in eclipse I’m doing it in my browser to the JBoss server running inside of eclipse. It is acting like I have a bunch of conditional breakpoints installed but I don’t have any.

Mike

[Panagiotis Korros]

I have notiched it too. It has to do with the debbuger i think.

[myoungstrom]

Scott,

So, what we have gathered so far is this problem didn’t exist in 3.8.4 with 3.1 M7 and pkorros and I believe it is probably related to the debugger in some way. This is a difficult problem to try and regularly reproduce so I don’t think I can provide a sure fire list of steps other than to tell you to try doing some pretend developing with JBoss 4.0.2. Do you know if there Is there anything else that we can do to help hunt down this problem?

Mike

[Riyad Kalla]

Mike,
Do you have a ton of projects open? When your run your app servers in debug mode the debugger does scan across all open projects for break points and such, so this operation isn’t cheap. To speed things up try closing projects you aren’t working on.

[myoungstrom]

In my workspace I have about 20 projects open. Next time I have the problem I’ll try closing them all to see if that helps at all maybe that will help tell us something about this problem. Do you have any other ideas of things I can try to help narrow down the problem more?

Mike

[Riyad Kalla]

Atleast giving Eclipse 256m of memory using the -vmargs command line argument, but I think you are already doing that?

[myoungstrom]

Next piece of evidence in this strange problem. If I notice the problem happening and I close all of my projects and re-open them then the problem appears to go away for a while.

Mike

[Riyad Kalla]

Mike,
How many projects we talking here, also how big?

[paasiala]

Sorry. wrong forum.

[ArmacSystems]

Hi,

just wanted to add my “me too” to this. The situation were seeing is also with 3.1 and 4.0M2, but we’ve also seen it on eclipse 3.0 and the relevant MyEclipse plugin. The server that we’re running in JBoss 3.2.6 with JDK 1.4.2_06. When running our suite of unit tests in Eclipse, with JBoss in debug mode, the tests take over 90 minutes. Using Eclipse 2.1 they are only taking 15 minutes. Switching debug mode off for JBoss, the tests only take about 20 minutes, so I think it’s fair to assume it is the debugger.

In terms of open projects, I have 6 open, 1 ear project, 1 ejb project, 1 web project, 1 library code project, 1 resource archive project and 1 deployment project. There isn’t a huge amount of code, and no more than when we use Eclipse 2.1, and the projects can’t be closed as they’re all involved in the deployment.

JBoss runs with -Xmx512m vmarg, but eclipse doesn’t have any modified options, the default is for 512M.

This is a pretty bad scenario for us, we can’t test our application if we upgrade to eclipse 3.1. Why would the debugger be affected so much, is there anyway we can improve this speed?

Thanks,

Mark

[Riyad Kalla]

but eclipse doesn’t have any modified options

This means you are running Eclipse with a 64mb heap which is the JVM default, please adjust your Eclipse shortcut and add:
-vmargs -Xmx256m

at the least, the more the better. See if that improves the situation.

[ArmacSystems]

Hi Riyad,

The shortcut that MyEclipse installs to execute Eclipse has the -vmargs -Xmx512M already set.

Mark

[Riyad Kalla]

Mark,
While the amount of projects you have open certainly doesn’t sound problomatic, are any of them inordinately large? 10s of thousands of files per project maybe?

[Author]

Posts