[csell]

Hello,

We just started to use the MyEclipse WebTools on a fairly large web project, by adding/enabling the MyEclipse web capabilities to the project. I had been wary of doing this, because I had previously heard about instabilities and other problems, but it became unavoidable because MyEclipse was the tool of choice, ad dealing with all the JSPs without tag completion was becoming tedious.

But, alas, we are now experiencing extreme problems when eclipse rebuilds the entire project (e.g., after a “clean project”). The rebuild takes endlessly, so that I always end up killing eclipse. When I call up the progress view, I see that the time is taken by processing JSP files, which goes very slow (0,5-1 seconds per file). It also seems the same files get processed over and over again.

Also, I initially had IOErrors in the error log, which happened when invoking javac as part of jasper invocations (obviously JSP processing again). I then put javac into the PATH, which resolved the error messages, but still left everything so slow that killing the IDE and disabling MyEclipse was the only solution.

There are a lot of rather complex JSP pages in our project. What can we do to get MyEclipse working in this context?

thanks,
Christian Sell

[csell]

ah, and this:

– System Setup ——————————-
Operating System and version: Windows XP SP2
Eclipse version: 3.01
Eclipse build id: M200409161125
Fresh Eclipse install (y/n): y
If not, was it upgraded to its current version using the update manager?
Other installed external plugins:
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*: 8
MyEclipse version: 3.8.4
Eclipse JDK version: 1.4.2_07
Application Server JDK version: 1.4.2_07
Are there any exceptions in the Eclipse log file? Yes

[Scott Anderson]

Christian,

If the time (.5-1sec) to compile each JSP page is too much given the number of pages in your project, I’d suggest simply turning off JSP validation for that project by right-clicking in the Package Explorer View on the project and selecting Properties > MyEclipse Validation > Override workbench settings and unchecking JSP validation. From that point forward, JSP will no longer be compiled. Of course the downside is that errors can’t be found when you modify and save your pages automatically. However, you can still check pages manually by right-clicking and selecting MyEclipse > Run Validation on the file / folder to manually run validation on just a subset of files periodically, if you like.

One other thing to check is whether or not you’re giving Eclipse enough heap space given the size of your projects. The time could be due to lots of swapping. To start with a larger heap, you can change the Eclipse commandline options to add:
eclipse.exe -vmargs -Xms128M -Xmx512M

Either option, or both, should make a large difference in the rebuild times.

[csell]

Hello,

I have changed the eclipse startup args to -Xmx512m. That does not seem to affect the compile times, which really are at ~ 2 sec per file. While the compile takes place, there is no progess indication (always at 6%), but I can see the files being named one after the other. After 20 minutes of waiting, it seems about time to kill eclipse again.

After disabling JSP validation, and restarting eclipse, I again ran a “clean, rebuild”. Now, this is what I see in the error log:

*** ERROR ***: Mon Feb 28 10:28:21 CET 2005 java.lang.StackOverflowError

I guess there is no free/cheap lunch…
christian

[Riyad Kalla]

Christian,
I was able to reproduce this bug and have filed it as a high priority for us to look at. We appologize for the trouble and hope to get this fixed soon after EclipseCon is done.

[Author]

Posts