org.eclipse.core.runtime.CoreException: Exception retrieving system properties

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Eclipse Bugzilla by as.maps, 1 year ago
via Eclipse Bugzilla by eclipse, 1 year ago
Unable to retrieve system properties
via Eclipse Bugzilla by pascal, 1 year ago
Unable to retrieve system properties
via Eclipse Bugzilla by steffen.pingel, 1 year ago
Unable to retrieve system properties
via Eclipse Bugzilla by markus_keller, 1 year ago
Exception retrieving system properties: C:\java\weme-win-x86-ppro10_6.1.1.20061110-161633\bin\javaw.exe -showversion -Xmx16m -classpath C:\e\w\master\git\eclipse.jdt.debug\org.eclipse.jdt.launching\lib\launchingsupport.jar org.eclipse.jdt.internal.launching.support.LegacySystemProperties java.specification.name java.specification.version java.version
via harmony-alerts by nomail@intel.com, 1 year ago
Unable to retrieve system properties
org.eclipse.core.runtime.CoreException: Exception retrieving system properties
at org.eclipse.jdt.launching.AbstractVMInstall.abort(AbstractVMInstall.java:500)
at org.eclipse.jdt.launching.AbstractVMInstall.evaluateSystemProperties(AbstractVMInstall.java:445)
at org.eclipse.jdt.internal.launching.environments.ExecutionEnvironmentAnalyzer.isFoundation1_0(ExecutionEnvironmentAnalyzer.java:150)
at org.eclipse.jdt.internal.launching.environments.ExecutionEnvironmentAnalyzer.analyze(ExecutionEnvironmentAnalyzer.java:96)
at org.eclipse.jdt.internal.launching.environments.Analyzer.analyze(Analyzer.java:40)
at org.eclipse.jdt.internal.launching.environments.EnvironmentsManager.analyze(EnvironmentsManager.java:337)
at org.eclipse.jdt.internal.launching.environments.EnvironmentsManager.vmAdded(EnvironmentsManager.java:376)
at org.eclipse.jdt.launching.JavaRuntime.fireVMAdded(JavaRuntime.java:2373)
at org.eclipse.jdt.launching.JavaRuntime.initializeVMs(JavaRuntime.java:2744)
at org.eclipse.jdt.launching.JavaRuntime.getVMInstallTypes(JavaRuntime.java:532)
at org.eclipse.jdt.internal.launching.environments.EnvironmentsManager.initializeCompatibilities(EnvironmentsManager.java:234)
at org.eclipse.jdt.internal.launching.environments.ExecutionEnvironment.init(ExecutionEnvironment.java:177)
at org.eclipse.jdt.internal.launching.environments.ExecutionEnvironment.getDefaultVM(ExecutionEnvironment.java:214)
at org.eclipse.jdt.internal.launching.JREContainerInitializer.resolveVM(JREContainerInitializer.java:173)
at org.eclipse.jdt.internal.launching.JREContainerInitializer.resolveVM(JREContainerInitializer.java:140)
at org.eclipse.jdt.internal.core.JavaModelManager.initializeContainer(JavaModelManager.java:2843)
at org.eclipse.jdt.internal.core.JavaModelManager$11.run(JavaModelManager.java:2749)
at org.eclipse.jdt.internal.core.JavaModelManager.initializeAllContainers(JavaModelManager.java:2789)
at org.eclipse.jdt.internal.core.JavaModelManager.getClasspathContainer(JavaModelManager.java:1873)
at org.eclipse.jdt.core.JavaCore.initializeAfterLoad(JavaCore.java:3886)
at org.eclipse.jdt.internal.ui.InitializeAfterLoadJob$RealJob.run(InitializeAfterLoadJob.java:36)

Users with the same issue

You are the first who have seen this exception.

Write tip

Know the solutions? Share your knowledge to help other developers to debug faster.