[DaftMule]

This issue is starting to drive me mad! Symptoms as follows:

Java/JSP web project utilising JSTL. When editing a JSP, as I type a line of jstl, as soon as I get to the opening speech quotes ” (pressing shift-2), the editor locks up for up to 20 seconds before printing the opening quote on the page.

e.g. to get from:

<c:out value=

to…

<c:out value="

…takes about 20 seconds.

This happens no matter whether I open the JSP using the JSP Editor, Visula Editor or Text Editor. I have tried disabling all validation in the properties.

I have also noticed that as the lockup occurs, the cpu usage for myeclipse.exe goes up to 50% then back to 0 once the control returns again to the IDE.

I am mystified as this has only recently started happening. I know the XML editor has always been a bit rubbish and laggy, but this is a new one for me to get it in the JSP’s.

Anyone else have this issue?

[DaftMule]

Sorry…forgot to mention that this is MyEclipse v 7.1.1

[support-joy]

DaftMule,

Sorry for the inconvinience. We are working on improving the performance for our next release of MyEclipse 7.5, tentatively due this month end. For pointers, can you copy and paste your installation details? You can find it under MyEclipse > Installation Summary > Installation Details.
How many projects are present in your current workspace? What are the type of projects you work on? What is their size? This will help give an understanding of your current configuration.

Can you check if the performance is better by switching to a new workspace?

[DaftMule]

Installation summary as follows:

*** Date:
18 May 2009 10:06:26 o’clock BST

** System properties:
OS=WindowsXP
OS version=5.1.0
Java version=1.5.0_11

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 7.1.1
Build id: 7.1.1-20090310

*** Eclipse details:
MyEclipse Enterprise Workbench

Version: 7.1.1
Build id: 7.1.1-20090310

Eclipse Platform

Version: 3.4.1.r341_v20080731-9I96EiDElYevwz-p1bP5z-NlAaP7vtX6Utotqsu
Build id: M20080911-1700

Eclipse Java Development Tools

Version: 3.4.1.r341_v20080709-0800-7o7tEAfEF_U5qyUgrb2HAp539P97
Build id: M20080709-0800

Eclipse Graphical Editing Framework GEF

Version: 3.4.1.v20080806-67718083A56B4H2A3213573
Build id: 200809101400

Eclipse RCP

Version: 3.4.100.r341_v20080814-989JESIEdAciFYfkZZsBfSwQ2341
Build id: M20080703-0800

Eclipse Plug-in Development Environment

Version: 3.4.1.r341_v20080731-7T7U0E9mlRIuGUYviF_VP
Build id: M20080703-0800

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Java\eclipse\Genuitec\MyEclipse 7.0\myeclipse.exe
-name
Myeclipse
–launcher.library
C:\Java\eclipse\Genuitec\MyEclipse 7.0\../Common\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731\eclipse_1115.dll
-startup
C:\Java\eclipse\Genuitec\MyEclipse 7.0\../Common\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar
-clean
-configuration
configuration
-vm
C:\Java\eclipse\Genuitec\Common\binary\com.sun.java.jre.win32.x86_1.5.0.011\bin\client\jvm.dll

I have 39 projects in my current workspace…the majority are web projects in the same manner…Java, JSP’s (utilising JSTL). Others are just general Java projects. Nothing particularly fancy about any of them. Total workspace size on disk is about 2gb. Project sizes vary from about 40mb to 70mb (including jars etc).

Even if I close all projects except the one I am working on, I still have the same problem.

I have tried a new workspace and I still get the same problem.

This feels like an issue where the JSTL is being validated as I type and the validator is locking up as soon as I type the opening quotes. However, as I say, even if I turn off all validation, the problem persists. I don’t get any lockup while typing anything else in the jsp…it is just that opening quote.

[support-eugene]

Can you check memory state? To open heap monitor open on the main menu: MyEclipse->Utilities->Show Heap Status. Please post the free/total memory stats it shows when the lock-up occurs.

[DaftMule]

Memory usage before starting to type:

89M of 174M

As I type the test

<c:out value=""/>

, the memory increases to:

100M of 174M

but the display of memory used jumps to that value once control returns after the lockup. As I finish typing it claws back a few meg of memory.

Obviously this varies a bit but there is definitely a spike as I type the opening speech quotes.

An observation I have made….typing the jstl text just before the closing </form> tag (i.e. at the bottom of the jsp page) causes no lag/lockup at all. Yet typing the text at the top of the page, just inside the opening <form> tag, causes a lockup for up to 20 seconds.

The jsp is just over 1,000 lines long currently (still some rationalisation to do!) but there is definitely a trend that the further down the page you go, the shorter the period of lockup until the point where no lockup occurs at all.

[DaftMule]

Oh…max heap size is quoted as 508M

[Loyal Water]

DaftMule,
Can you close all projects you dont need open at the time of editing and reopen the editor and see if performance is better… if so, we are working on that fix *literally* right now. This should be fixed for the 7.5 release.

[DaftMule]

@support-nipun wrote:

DaftMule,
Can you close all projects you dont need open at the time of editing and reopen the editor and see if performance is better… if so, we are working on that fix *literally* right now. This should be fixed for the 7.5 release.

I have closed all projects except the one I am working on, restarted the IDE and it makes no difference. Still the delay of 10 to 20 seconds when I type the JSTL at the top of the jsp and no delay when I type it at the bottom of the jsp

[support-joy]

DaftMule,

Will it be possible for you to share your project with JSP? I am unable to reproduce this at my end. If you can share your project, I can have a dev team member investigate more on this. You can send a mail to support@genuitec.com with your project as attachment. Please add ATTN: Joy in the subject and refer to this post in your mail.

[DaftMule]

Hi Joy,

Sorry, I wouldn’t be able to share any of my projects with you due to client confidentiality.

I will see if I can get some time to put together a new project “foo” to see if it gets the same problem. If so, I should be able to pass that on to you.

Is there any way of getting the editor to do more debug logging? I have added the “-debug” flag to my .exe shortcut, but that isn’t logging anything when the lockups occur.

[support-joy]

DaftMule,

MyEclipse doesn’t provide any special logging feature. You can try using log4j, my 2 cents.
I have an update from my dev team members that JSTL related performance improvements are being added to the next release of ME7.5. If you could share your project/test project, it will help us test this scenario too.

[DaftMule]

Joy,

I have sent you an email with a test project attached. I get the lag issue when editing the jsp in the project.

As this is lag on typing the opening speech quote ” it perhaps indicates that, when typed at the top of a long jsp page, opening the quotes is causing some sort of behind the scenes validation parser to scan the whole of the rest of the jsp text which it believes is now part of that jstl syntax. I say this because I notice that once the opening speech quote appears on the page, any standard text on the jsp page changes colour from black normal text to blue itallics. Closing the quotes then changes the text back to black normal…but the change back is much quicker. If I then delete the closing quotes again, I get the lockup and the change of text to blue itallics once more.

Maybe this is something to do with the Styling application in jsp’s??

[DaftMule]

By the way, I notice in re-reading my original post that I said this issue happens even if I edit using the text editor. Not sure why I said that as there is no issue with lag when editing using the text editor option…it only occurs when using the specific JSP editors.

[support-joy]

Thank you Adam for sending out the test project. I am able to reproduce this issue using the sample application. I have filed a PR for the dev team members to investigate further.

[Author]

Posts