Community
Participate
Working Groups
Situation: We have a maven2/testng managed project. We're busy getting Eclipse to do performance profiling. As there is no TestNG profile possibility, we're trying to get 3.3RC2 to run the TestNG main function. If we go to profile -> open profile dialog -> doubleclick java application -> and then "main class" "search" Eclipse crashes hard, no logs, no message, just process termination.
What plug-ins do you have in your workbench? By default, profile is disabled in the Eclipse SDK (as no profiler is provided).
Does the same happen from the debug or run dialog? (I was not able to reproduce using the SDK).
Version: 3.3.0 Build id: I20070525-1350 Lots of plugins installed, most are from the eclipse europa repository and nearly all are java related: BIRT, JPA, DTP, EMFT, TPTP, UML2, WTP. The only others are maven2, testng en subclipse. (all latest versions from their online repositories) The run and debug have no problems running the configuration. Furthermore we've played around a bit and the error is consistent, whichever button, check or option is used in the profile tab. The crash only happens after you select the lauch settings (so opening the profile screen without actually doubleclicking on the configuration is fine). We have however found some interesting files. Please see the .log file at the end of this message for what seems to be the crash log. Some files below: [configuration\.settingsorg.eclipse.ui.ide] #Sun Jun 03 10:52:56 CEST 2007 RECENT_WORKSPACES_PROTOCOL=2 MAX_RECENT_WORKSPACES=5 SHOW_WORKSPACE_SELECTION_DIALOG=false eclipse.preferences.version=1 RECENT_WORKSPACES=D\:\\Stocketeer\\Workspace,C\:\\Users\\Dennis\\workspace [eclipse.ini] -showsplash org.eclipse.platform --launcher.XXMaxPermSize 256m -vmargs -Xms40m -Xmx256m [In workspace found a .log file] !ENTRY org.eclipse.tptp.platform.iac.administrator 4 0 2007-06-04 21:15:55.760 !MESSAGE unknown protocol: d !STACK 0 java.net.MalformedURLException: unknown protocol: d at java.net.URL.<init>(Unknown Source) at java.net.URL.<init>(Unknown Source) at java.net.URL.<init>(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLVersionDetector.determineDocVersion(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source) at javax.xml.parsers.DocumentBuilder.parse(Unknown Source) at org.eclipse.tptp.platform.iac.administrator.internal.common.AdminUtil.parseFile(AdminUtil.java:79) at org.eclipse.tptp.platform.iac.administrator.internal.common.AdminUtil.isConfigurationValid(AdminUtil.java:643) at org.eclipse.tptp.platform.iac.administrator.internal.startstop.AutoStartStop.startIAC(AutoStartStop.java:81) at org.eclipse.hyades.internal.execution.local.control.NodeImpl.connect(NodeImpl.java:283) at org.eclipse.hyades.security.internal.util.BaseConnectUtil.insecureConnect(BaseConnectUtil.java:369) at org.eclipse.hyades.security.internal.util.BaseConnectUtil.connect(BaseConnectUtil.java:255) at org.eclipse.hyades.security.internal.util.BaseConnectUtil.connect(BaseConnectUtil.java:540) at org.eclipse.tptp.platform.common.ui.trace.internal.util.PDCoreUtil.profileConnect(PDCoreUtil.java:827) at org.eclipse.tptp.trace.ui.internal.launcher.deleg.application.PIDelegateHelper$JVMVersionDetector.run(PIDelegateHelper.java:473) at java.lang.Thread.run(Unknown Source) !SESSION 2007-06-04 21:16:42.156 ----------------------------------------------- eclipse.buildId=I20070525-1350 java.version=1.6.0_01 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=nl_NL Command-line arguments: -os win32 -ws win32 -arch x86 !ENTRY org.eclipse.core.resources 2 10035 2007-06-04 21:16:43.787 !MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes. !ENTRY org.eclipse.core.resources 2 1 2007-06-04 21:17:03.663 !MESSAGE Skipping builder 'org.hibernate.eclipse.console.hibernateBuilder' for project 'Stocketeer-EJB3'. Either the builder is missing from the install, or it belongs to a project nature that is missing or disabled.
What VM are you using to run Eclipse?
And which Vista? I just tried this with RC3 on Vista business and I had no such problem.
Java: java version "1.6.0" Java(TM) SE Runtime Environment (build 1.6.0-b105) Java HotSpot(TM) Server VM (build 1.6.0-b105, mixed mode) Vista: Microsoft Windows [Version 6.0.6000] We initially didn't have any problems either. But it all started after playing around with the new Eclipse. I'm guessing that the "java.net.MalformedURLException: unknown protocol: d" isn't something that happens normally (d isn't a legal protocol). We'll try RC3 and let you know.
Vista Business btw
The exception from comment#3 should be reported to TPTP - but I don't think that it caused the hard crash. Are there any VM logs in your eclipse directory associated with the crash? Generally, a hard crash is associated with some sort of exception in a dll.
As well, does the same problem happen if you run Eclipse on a 1.4 or 1.5 VM?
Tried the 3.3RC3, same problem. Started out from new empty workspace, imported project, added above modules, predded the profiler button, add new java application and boom, crash. Again nothing to work with, I've uploaded the complete .log file for you.
Created attachment 70605 [details] Workspace log file
I just had the same problem on a laptop running Windows XP. I've tried several things and I believe I was able to fix it by moving the location of my TPTP installation to a directory without any whitespace. Originally, when I tried to profile a Java application, TPTP attempted to get the possible profile configurations and then crashed without any warning.
Dennis, is it possible that you also have TPTP in place with spaces in the path? If you try the fix mentioned in comment 12 does it work?
Email from Dennis: "Michael, Yes there was a space in the path. Some initial testing solved the problem here when moving eclipse to a non-space path. Sorry for the late reply. Regards" moving to TPTP for comment
This seems to be an IAC configuraiton problem on Eclipse path with space.
Can I just point out that a space in path name is pretty common on Windows? It seems like an easy fix - do you think you'll be able to fix it soon?
Created attachment 76649 [details] patch Hi Samson, Could you please check the patch in? Thanks.
Patch checked in.
Resolving as fixed
*** Bug 202341 has been marked as a duplicate of this bug. ***
Does this patch fix the underlying 'spaces in path' problem, or merely hide the symptom? Is this fixed in another bug? The parseFile(...) method in AdminUtil doesn't handle spaces w/ Java 6 and Vista and throws the MalformedURLException (and yet handles them fine w/ Java 6 XP). The solution to the path spaces bug is to change the 'document = builder.parse(fileName);' line to 'document = builder.parse(new File(filename));' in AdminUtil. Putting the filename in File form allows the parser to locate it properly.
The patch fixes the provided symptom - crash of Eclipse. Problem with spaces in Eclipse's path could fixed by the #201819.
I'm still experiencing this problem using TPTP 4.4.1 (total Eclipse crash).
*** Bug 215107 has been marked as a duplicate of this bug. ***
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
