- This topic has 41 replies, 11 voices, and was last updated 15 years, 6 months ago by Riyad Kalla.
-
AuthorPosts
-
innogateMemberThis message has not been recovered.
innogateMemberAny activity on this issue? I’m afraid this behaviour is pretty annoying. We now work with our J2EE projects closed most of the time, which can be no long term solution.
Is there any hint of a time frame when this issue will be resolved?
Riyad KallaMemberWe *think* we have narrowed down this poor performance. There are just a few things we need to check.
innogate, for the projects that are giving you poor performance, if you right-click and go to Properties, then check the MyEclipse node, which icons are lit up? Also if you expand the MyEclipse NOde, do you have a “JavaScript” sub-node?
innogateMember@support-rkalla wrote:
innogate, for the projects that are giving you poor performance, if you right-click and go to Properties, then check the MyEclipse node, which icons are lit up? Also if you expand the MyEclipse NOde, do you have a “JavaScript” sub-node?
The Project that gives us poor performance is a J2EE EAR project. The performance is back to normal again when we close it.
There is only one icon lit up on the MyEclipse properties: EAR
The MyEclipse node has no javascript subnode. Available subnodes are:
– EAR
– Task Tags
– UML1
– Validation, and below that “Excluded Resources”Some further impressions for what their worth:
Performance is even worse when working on an offline workstation. I think this is because of the HTTP download process that I saw in the stacktrace posted earlier. When I’m offline it seems to block all further UI operations until it runs into timeout. This happens every time I move the focus on the package explorer.If there is anything more I can do to help you, just let me know.
Riyad KallaMemberOk that’s even weirder… the EAR project is just a meta-project, it’s not intended to have any source artifacts in it, which means almost no validators on it, but if *that* project is the one causing all the trouble… hmmm.
Could you try this…
File > Swtich Workspace > C:\tempworkspace
Then using File > Import > Existing Project, and point at the EAR and the supporting modules from your existing workspace, and make sure the “Copy into new workspace” is checked, then import all those projects, do whatever configuration in that workspace that you need to get them to build (e.g. JRE registrations) and then see if performance is crumby in the new workspace too?
Nailing down what behaviors is causing this performance hickup is turning out to be slippery like an eel…
innogateMemberSorry for the delay. I did as you said and created a new workspace, imported my EAR project and all it’s dependent modules. Set classpath variables until all build errors were gone.
Restarted Eclipse. Going to package explorer and move focus across the entries with arrow up/down buttons. Everything is fast as it should be.
Open a java file in editor. Make a minor change and save it..
Going to package explorer and moving focus is slow again. Takes a second or two to change focus between two entries.
Taking a thread dump while package explorer delay exposes the following stack trace again:
java.lang.Thread.State: RUNNABLE
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:258)
at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
– locked <0xf1563820> (a java.io.BufferedInputStream)
at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:687)
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:632)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1049)
– locked <0xf15622f8> (a sun.net.www.protocol.http.HttpURLConnection)
at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown Source)
at org.apache.xerces.impl.XMLEntityManager.startDTDEntity(Unknown Source)
at org.apache.xerces.impl.XMLDTDScannerImpl.setInputSource(Unknown Source)
at org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:453)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:810)
at org.jdom.input.SAXBuilder.build(SAXBuilder.java:789)
at com.genuitec.eclipse.core.util.JDOMUtil.parseFile(JDOMUtil.java:159)
at com.genuitec.eclipse.j2eedt.core.EARProject.loadDeploymentDescriptorData(Unknown Source)
at com.genuitec.eclipse.j2eedt.core.EARProject.initEARDeploymentDescriptorManager(Unknown Source)
at com.genuitec.eclipse.j2eedt.core.EARProject.<init>(Unknown Source)
at com.genuitec.eclipse.j2eedt.core.EARProject.<init>(Unknown Source)
at com.genuitec.eclipse.j2eedt.core.J2EECore.getEARProjectsList(Unknown Source)
– locked <0xd633cd08> (a com.genuitec.eclipse.j2eedt.core.J2EECore)
at com.genuitec.eclipse.j2eedt.core.J2EECore.getEARProject(Unknown Source)
at com.genuitec.eclipse.j2eedt.core.J2EECore.getJ2EEProject(Unknown Source)
at com.genuitec.eclipse.ast.deploy.core.ui.action.DeploymentMgmtActionDelegate.selectionChanged(Unknown Source)
at org.eclipse.ui.internal.PluginAction.refreshEnablement(PluginAction.java:206)
at org.eclipse.ui.internal.PluginAction.selectionChanged(PluginAction.java:277)
at org.eclipse.ui.internal.PluginAction.selectionChanged(PluginAction.java:299)
at org.eclipse.ui.internal.AbstractSelectionService.fireSelection(AbstractSelectionService.java:156)
at org.eclipse.ui.internal.AbstractSelectionService$1.selectionChanged(AbstractSelectionService.java:62)
at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:162)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.core.runtime.Platform.run(Platform.java:880)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:160)
at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2062)
at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1138)
at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1168)
at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:227)
at org.eclipse.jface.util.OpenStrategy.access$3(OpenStrategy.java:221)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:388)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
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:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
at org.eclipse.equinox.launcher.Main.main(Main.java:1212)It seems that even a minor edit operation introduces this behaviour. If I interpret class/method names correctly, then moving the package explorer focus seems to trigger the parsing of the EAR deployment descriptor each time again. And in this parsing it seems as if there is some HTTP loading going on, maybe to load the DTD of the deployment descriptor. This would explain why the performance is even worse when my workstation is offline, because it then waits for a timeout to happen.
support-joyMemberWhat is the version of ubuntu you are using?
check this post https://www.genuitec.com/forums/topic/myeclipse-7-0-installer-hangs-on-ubuntu-8-10/&highlight=
innogateMemberHi Joy, first thanks for your help.
Well, I’m using Ubuntu 8.10, thats right. But I would be very suprised to hear that it cannot run Eclipse 3.4, because besides this issue here – which does not seem to be OS-related – it runs flawlessly and was also installed without problems.
Also I think that on that post you mentioned the ubuntu launchpad issue that user rahible found was misunderstood. It merely says that it is the wrong place to ask for support when the eclipse version used is not the one from the ubuntu repository. Becauce that launchpad page belongs to the ubuntu eclipse package.
innogateMemberPerformance is actually back to normal even when I keep the EAR project open but rename “application.xml” to “application.xml.off” or the such. This file definitely plays an important role in the problem.
kozmavilmosMemberAfter doing some tests I ended up with the next:
Conditions:
——————
– MyEclipse 7.0 Build id: 7.0-20081201
– OS: XP
– No EAR projects, but had some web projects, and Java projects.Conclusions:
—————–
– There seems to be no relation between performance and state of workspace (upgraded from earlier MyEclipse version or newly created)
– No relation between performance and OS
– The more Web projects are open the slower is the selection cursor in package explorer.This bug is realy annoying and is unknown in normal Genymede, so please, please fix this.
innogateMemberI sniffed the HTTP traffic with wireshark while the delay happens and can see that the following URL is loaded:
http://java.sun.com/dtd/web-app_2_3.dtd
Which of course is the DTD of a Web Project’s web.xml. I have exactly one Web Project belonging to the problematic EAR project that uses this DTD.
Maybe, when a Web Project is not part of any EAR, this behaviour is triggered by the Web Project itself?
Riyad KallaMemberinnogate, excellent digging. I’m kicking this back to the dev team to figure out what’s going on here.
Riyad KallaMemberGuys we found out what was going on here and got a fix into 7.1 for you — thanks for your patience while we ran this down.
jordan.parkerMemberGreat Riyad, thank you for the update. Is there any time frame for the 7.1 release (even a rough time frame would be nice)?
support-joyMemberjordan.parker,
7.1 release is going through a rigorous QA process. The likely release date is in a week or 2. Thank you for your patience.
-
AuthorPosts