[Riyad Kalla]

Have you all upgraded to 4.0.3? If so, I would suggest a separate testing install of Eclipse 3.1.1 and MyEclipse 4.1M1 later today when it is released (note, this is for testing only, I am not suggesting you deploy 4.1M1 out into production environments).

[Riyad Kalla]

Note: the reason progress on this is dragging is that using all of our test cases internally we are unable to reproduce a consistent state where the JSP editor is just unusably slow.

If ANY of you can send us a web project that exhibits this problem it would help us get this problem fixed as we would be able to narrow down the culprit quite a bit faster.

Note: In the past, many times slow editing can be fixed by increasing the memory AND permspace available to Eclipse using the following command line args:

-vmargs -Xms128m -Xmx256m -XX:PermSize=128M

[lowhm]

Hi guys,

I’m trying to reproduce this problem as suggested by rkalla.

However, amazingly, the problem seems to disappear.
😀

These are the following steps I have done in between the time when the problem still exists and after it is gone.
1) Upgrade to 4.0.3
2) Copy the jsp that is having the problem to a new page
3) Remove all the content in the copy of new jap to only the directives <%@ … %> and a single scriplet <% %>
4) Try to use the code completion in the scriptlet e.g. System.
At this point, the code completion works without the problem
5) Switching back to the jsp that has the problem and try the code completion again, the problem seems to go away.

For those of you having the problem, you can try it out and post to see if you can have it resolved.
Would be great to let the rest of the guys know if this really solve the problem.

Cheers.

Han Ming

[lowhm]

Hi,

Just an additional note for the support.

I found this in my .log, so I was thinking if it is helpful for you to at least know what might be the cause.

Cheers.

Han Ming

!ENTRY org.eclipse.ui 4 0 2005-11-07 18:29:32.749
!MESSAGE Warning: Detected recursive attempt by part com.genuitec.eclipse.webdesigner.jsp to create itself (this is probably, but not necessarily, a bug)
!STACK 1
org.eclipse.ui.PartInitException: Warning: Detected recursive attempt by part com.genuitec.eclipse.webdesigner.jsp to create itself (this is probably, but not necessarily, a bug)
    at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:543)
    at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:214)
    at org.eclipse.ui.internal.EditorManager.findEditor(EditorManager.java:477)
    at org.eclipse.ui.internal.EditorManager.findEditor(EditorManager.java:402)
    at org.eclipse.ui.internal.EditorManager.findEditor(EditorManager.java:372)
    at org.eclipse.ui.internal.WorkbenchPage.findEditor(WorkbenchPage.java:1772)
    at com.genuitec.eclipse.core.util.EditorUtil.getEditorForInput(Unknown Source)
    at com.genuitec.eclipse.core.util.EditorUtil.checkConflictingEditor(Unknown Source)
    at com.genuitec.eclipse.webdesigner2.HTMLMultiPageEditorPart.init(HTMLMultiPageEditorPart.java:873)
    at org.eclipse.ui.internal.EditorManager.createSite(EditorManager.java:773)
    at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:572)
    at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:365)
    at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:552)
    at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:214)
    at org.eclipse.ui.internal.EditorManager.findEditor(EditorManager.java:477)
    at org.eclipse.ui.internal.EditorManager.findEditor(EditorManager.java:402)
    at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2274)
    at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2258)
    at org.eclipse.ui.internal.WorkbenchPage.access$9(WorkbenchPage.java:2250)
    at org.eclipse.ui.internal.WorkbenchPage$9.run(WorkbenchPage.java:2236)
    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
    at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2231)
    at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2212)
    at org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility$1.run(SourceLookupFacility.java:353)
    at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
    at org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility.openEditor(SourceLookupFacility.java:362)
    at org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility.openEditor(SourceLookupFacility.java:278)
    at org.eclipse.debug.internal.ui.sourcelookup.SourceLookupFacility.display(SourceLookupFacility.java:209)
    at org.eclipse.debug.ui.DebugUITools.displaySource(DebugUITools.java:673)
    at org.eclipse.debug.internal.ui.views.launch.LaunchView$SourceDisplayJob.runInUIThread(LaunchView.java:209)
    at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:93)
    at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
    at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
    at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3057)
    at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2716)
    at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699)
    at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663)
    at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367)
    at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143)
    at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103)
    at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334)
    at org.eclipse.core.launcher.Main.basicRun(Main.java:278)
    at org.eclipse.core.launcher.Main.run(Main.java:973)
    at org.eclipse.core.launcher.Main.main(Main.java:948)
!SUBENTRY 1 org.eclipse.ui 4 0 2005-11-07 18:29:32.765
!MESSAGE Warning: Detected recursive attempt by part com.genuitec.eclipse.webdesigner.jsp to create itself (this is probably, but not necessarily, a bug) 

[adeimer]

rkalla,
I have setup a small testproject where the problem occurs. Could you give me
an eMail address so I can mail it to you directly?

Rgds
Andreas

[Riyad Kalla]

Han, thank you for the report, we will look into the cause of that issue. The developer I asked about it said for now it’s harmless but he is working on fixing it.

Also, did you try adding the command line args I suggested above, or did you just upgrade to 4.0.3 and the problem went away? A lot of work was done in the 4.0.x releases to improve autocomplete speed so maybe that is what helped?

[Riyad Kalla]

Andreas,
Please email the project to support@genuitec.com ATTN Riyad, with a small description of how to reproduce this issue and a link to this forum post so I know why I’m receiving the attachment.

[Riyad Kalla]

Andreas,
I got your project from the PM system and opened it, I opened all the JSP pages and then switched to login.jsp. I tried editing in all portions of the page, by typing gibberish (e.g. aksdjaskldjalkjsd) and by trying to insert System.out statements using autocomplete. I tried at the top of the scriplet and at the bottom, I also tried at the top of all the includes and again at the bottom, editing was fast and the same speed in all locations.

Did you try the command line arguments I gave above?

 -vmargs -Xms128m -Xmx256m -XX:PermSize=128M

Additionally, what Build ID of Eclipse (Help > About) and MyEclipse ( Window > Prefs > MyEclipse ) are you using?

What is your hardware like?

[lowhm]

Hi all,

I’d just like to update on some more findings on this issue.

I found that it is very much related to the libraries you have configured for the project.
If you have weblogic.jar configured as a library and included it in your project, try to remove it and try again.

Ermm, the weblogic.jar is not exactly the offending jar.
Somehow, in a combination of jars, the auto-complete become very slow.

For my case, I have the following libraries.
Weblogic J2EE – weblogic.jar
Struts – All the struts jars
Commons – Our common EJB which consists of about 50 EJBs (each separate jar) + the helper classes for these EJBs

Even for an empty WebProject, if I include all these 3 libraries, the auto-complete immediately slows down. Backspace is also a pain when the code suggestion pop up is appearing.

However, removing any one of the 3 libraries, the auto-complete works quickly.
As the J2EE 1.3 Library Container has the J2EE API, thus, I can afford to take my Weblogic J2EE out of my build path.
That is my temporary solution to the problem, unless in the later part, I might discover that I have to use the weblogic.jar, then the problem will arise again.

I have tried the command line options, doesn’t help much.

Hope this information helps.

Cheers.

Han Ming

[Riyad Kalla]

Han,
You did find a current problem we are aware of, when you have a huge classpath (lots of classes) the autocomplete index becomes quite large (as you found) and really slows down. The bigger the JAR, the more classes, the slower the autocomplete. We made some improvements recently and will continue to optimize this functionality moving forward.

[adeimer]

rkalla,

I am using your vm parameters and the following versions:

Eclipse:
Version: 3.1.0
Build id: I20050627-1435

MyEclipse
Version 4.0.100 M1
Build id: 20051103-4.1-Milestone1

Even when installing 4.1m1 to a fresh installation of Eclipse, either 4.1 or 4.2m3, the editor is slow in the test project I sent you. When you remove the <% includes %> directives or reduce them, it affects the speed dramatically. I also noticed that when including a jsp that includes a jsp that includes a jsp, it also slows down the jsp editor.

Does this help?

Andreas

[adeimer]

rkalla, I forgot to mention my system: Two-Processor Pentium 4/3.0GHz with 2GB RAM.
Andreas

[Riyad Kalla]

Andreas,
Given your hardware I have no idea why you would be seeing any slow down with this project you sent me. Can you explain exactly what you mean by slow JSP editor. Is it just the autocomplete popup speed? Are the keystrokes actually entered slowly? etc?

[fiasco]

Hi,

I got this problem and was finding the way to solve it for a while (including reading this thread)
Finally, I can resolve this on serveral machinces and I’d like to share to u guys.

Try this easy 3 steps
– Upgrade eclipse from 3.1 to 3.1.1
– Upgrade myeclipse from 4.0.0 to 4.0.3
– Change start up argument int eclipse.ini to

-vmargs -Xms128m -Xmx512m -XX:PermSize=64M -XX:MaxPermSize=128M

After done those steps, jsp editor work a lot faster for my project. Hope this helps !

[Riyad Kalla]

fiasco,
Thank you for providing your steps for others.

[Author]

Posts