Eclipse Community Forums: Java Development Tools (JDT) » Can't create Java Run Configuration

Home » Language IDEs » Java Development Tools (JDT) » Can't create Java Run Configuration

Can't create Java Run Configuration [message #249131]

Tue, 30 October 2007 01:37

Eclipse User

Originally posted by: jmason1966.hotmail.com

This used to work ... about a month ago ... that was the last time I had
to create a new Java configuration. No idea what could have changed.

In Java perspective:
- Run / Run
- Right Click on Java Application and click "New" to create new
configuration
No configuration is created. There is a brief flash of something in the
bottom of the dialog box like it's going to create the new configuration
.. but then nothing happens

Using:
Ubuntu 7.04
Eclipse Project SDK 3.2.1.r322_v20070104
Java6 JRE

No idea where to even start looking for the cause of this. Any help
really, really appreciated.

James

Re: Can't create Java Run Configuration [message #249137 is a reply to message #249131]

Tue, 30 October 2007 08:48

Eclipse User

Originally posted by: merks.ca.ibm.com

James,

Have a look in the Error Log view for logged exceptions.

JM wrote:
> This used to work ... about a month ago ... that was the last time I
> had to create a new Java configuration. No idea what could have changed.
>
> In Java perspective:
> - Run / Run
> - Right Click on Java Application and click "New" to create new
> configuration
> No configuration is created. There is a brief flash of something in
> the bottom of the dialog box like it's going to create the new
> configuration . but then nothing happens
>
> Using:
> Ubuntu 7.04
> Eclipse Project SDK 3.2.1.r322_v20070104
> Java6 JRE
>
> No idea where to even start looking for the cause of this. Any help
> really, really appreciated.
>
> James
>

Re: Can't create Java Run Configuration [message #249152 is a reply to message #249137]

Wed, 31 October 2007 16:15

Eclipse User

Originally posted by: jmason1966.hotmail.com

Thanks. Found the log, but still pretty confused. The first ENTRY message
looks like a warning, but not sure if the second ENTRY is a warning or
just information. Wondering if this means there's an error with
"org.apache.xerces.dom.DocumentImpl.getXmlStandalone". I'm using a Xerces
jar in my program, but don't think that can be related, because I'm just
trying to create a run configuration at this stage ... so program wouldn't
even be loaded (right??). Or maybe this isn't even a warning? ... brain
hurts ....

!ENTRY org.eclipse.ui 4 4 2007-11-01 06:58:11.330
!MESSAGE Unhandled event loop exception

!ENTRY org.eclipse.ui 4 0 2007-11-01 06:58:11.331
!MESSAGE org.apache.xerces.dom.DocumentImpl.getXmlStandalone()Z
!STACK 0
java.lang.AbstractMethodError:
org.apache.xerces.dom.DocumentImpl.getXmlStandalone()Z
at
com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.setDocum entInfo(DOM2TO.java:373)
at
com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(DO M2TO.java:127)
at
com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(DO M2TO.java:94)
at
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl .transformIdentity(TransformerImpl.java:663)
at
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl .transform(TransformerImpl.java:709)
at
com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl .transform(TransformerImpl.java:313)
at
org.eclipse.debug.internal.core.LaunchManager.serializeDocum ent(LaunchManager.java:520)
at
org.eclipse.debug.internal.core.LaunchConfigurationInfo.getA sXML(LaunchConfigurationInfo.java:348)
at
org.eclipse.debug.internal.core.LaunchConfigurationWorkingCo py.writeNewFile(LaunchConfigurationWorkingCopy.java:209)
at
org.eclipse.debug.internal.core.LaunchConfigurationWorkingCo py.doSave0(LaunchConfigurationWorkingCopy.java:196)
at
org.eclipse.debug.internal.core.LaunchConfigurationWorkingCo py.doSave(LaunchConfigurationWorkingCopy.java:172)
at
org.eclipse.debug.internal.ui.launchConfigurations.CreateLau nchConfigurationAction.performAction(CreateLaunchConfigurati onAction.java:78)
at
org.eclipse.debug.internal.ui.launchConfigurations.AbstractL aunchConfigurationAction$1.run(AbstractLaunchConfigurationAc tion.java:103)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:67)
at
org.eclipse.debug.internal.ui.launchConfigurations.AbstractL aunchConfigurationAction.run(AbstractLaunchConfigurationActi on.java:106)
at
org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEv ent(BaseSelectionListenerAction.java:168)
at
org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:539)
at
org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:488)
at
org.eclipse.jface.action.ActionContributionItem$5.handleEven t(ActionContributionItem.java:400)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1085)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3180)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2856)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:820 )
at org.eclipse.jface.window.Window.open(Window.java:796)
at
org.eclipse.debug.internal.ui.launchConfigurations.LaunchCon figurationsDialog.open(LaunchConfigurationsDialog.java:1086)
at org.eclipse.debug.ui.DebugUITools$1.run(DebugUITools.java:38 3)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:67)
at
org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDia logOnGroup(DebugUITools.java:387)
at
org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDia logOnGroup(DebugUITools.java:329)
at
org.eclipse.debug.ui.actions.OpenLaunchDialogAction.run(Open LaunchDialogAction.java:80)
at
org.eclipse.debug.ui.actions.OpenLaunchDialogAction.run(Open LaunchDialogAction.java:99)
at
org.eclipse.ui.internal.PluginAction.runWithEvent(PluginActi on.java:254)
at
org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPl uginAction.java:229)
at
org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:539)
at
org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:488)
at
org.eclipse.jface.action.ActionContributionItem$5.handleEven t(ActionContributionItem.java:400)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1085)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3180)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2856)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1930)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1894)
at
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:422)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:95)
at
org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:78)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:92)
at
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:68)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:400)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336 )
at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
at org.eclipse.core.launcher.Main.run(Main.java:977)
at org.eclipse.core.launcher.Main.main(Main.java:952)

Re: Can't create Java Run Configuration [message #249183 is a reply to message #249152]

Thu, 01 November 2007 13:20

Eclipse User

Originally posted by: eclipse6.rizzoweb.com

JM wrote:
> Thanks. Found the log, but still pretty confused. The first ENTRY
> message looks like a warning, but not sure if the second ENTRY is a
> warning or just information. Wondering if this means there's an error
> with "org.apache.xerces.dom.DocumentImpl.getXmlStandalone". I'm using a
> Xerces jar in my program, but don't think that can be related, because
> I'm just trying to create a run configuration at this stage ... so
> program wouldn't even be loaded (right??). Or maybe this isn't even a
> warning? ... brain hurts ....

Is the Xerces JAR you're using for your program somehow making its way
onto the classpath that Eclipse is running with? For example, is it in
the ext/ directory of your JDK or JRE?

Hope this helps,
Eric

>
>
> !ENTRY org.eclipse.ui 4 4 2007-11-01 06:58:11.330
> !MESSAGE Unhandled event loop exception
>
> !ENTRY org.eclipse.ui 4 0 2007-11-01 06:58:11.331
> !MESSAGE org.apache.xerces.dom.DocumentImpl.getXmlStandalone()Z
> !STACK 0
> java.lang.AbstractMethodError:
> org.apache.xerces.dom.DocumentImpl.getXmlStandalone()Z
> at
> com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.setDocum entInfo(DOM2TO.java:373)
>
> at
> com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(DO M2TO.java:127)
> at
> com.sun.org.apache.xalan.internal.xsltc.trax.DOM2TO.parse(DO M2TO.java:94)
> at
> com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl .transformIdentity(TransformerImpl.java:663)
>
> at
> com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl .transform(TransformerImpl.java:709)
>
> at
> com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl .transform(TransformerImpl.java:313)
>
> at
> org.eclipse.debug.internal.core.LaunchManager.serializeDocum ent(LaunchManager.java:520)
>
> at
> org.eclipse.debug.internal.core.LaunchConfigurationInfo.getA sXML(LaunchConfigurationInfo.java:348)
>
> at
> org.eclipse.debug.internal.core.LaunchConfigurationWorkingCo py.writeNewFile(LaunchConfigurationWorkingCopy.java:209)
>
> at
> org.eclipse.debug.internal.core.LaunchConfigurationWorkingCo py.doSave0(LaunchConfigurationWorkingCopy.java:196)
>
> at
> org.eclipse.debug.internal.core.LaunchConfigurationWorkingCo py.doSave(LaunchConfigurationWorkingCopy.java:172)
>
> at
> org.eclipse.debug.internal.ui.launchConfigurations.CreateLau nchConfigurationAction.performAction(CreateLaunchConfigurati onAction.java:78)
>
> at
> org.eclipse.debug.internal.ui.launchConfigurations.AbstractL aunchConfigurationAction$1.run(AbstractLaunchConfigurationAc tion.java:103)
>
> at
> org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:67)
> at
> org.eclipse.debug.internal.ui.launchConfigurations.AbstractL aunchConfigurationAction.run(AbstractLaunchConfigurationActi on.java:106)
>
> at
> org.eclipse.ui.actions.BaseSelectionListenerAction.runWithEv ent(BaseSelectionListenerAction.java:168)
>
> at
> org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:539)
>
> at
> org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:488)
>
> at
> org.eclipse.jface.action.ActionContributionItem$5.handleEven t(ActionContributionItem.java:400)
>
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1085)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3180)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2856)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:820 )
> at org.eclipse.jface.window.Window.open(Window.java:796)
> at
> org.eclipse.debug.internal.ui.launchConfigurations.LaunchCon figurationsDialog.open(LaunchConfigurationsDialog.java:1086)
>
> at org.eclipse.debug.ui.DebugUITools$1.run(DebugUITools.java:38 3)
> at
> org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:67)
> at
> org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDia logOnGroup(DebugUITools.java:387)
>
> at
> org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDia logOnGroup(DebugUITools.java:329)
>
> at
> org.eclipse.debug.ui.actions.OpenLaunchDialogAction.run(Open LaunchDialogAction.java:80)
>
> at
> org.eclipse.debug.ui.actions.OpenLaunchDialogAction.run(Open LaunchDialogAction.java:99)
>
> at
> org.eclipse.ui.internal.PluginAction.runWithEvent(PluginActi on.java:254)
> at
> org.eclipse.ui.internal.WWinPluginAction.runWithEvent(WWinPl uginAction.java:229)
>
> at
> org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(ActionContributionItem.java:539)
>
> at
> org.eclipse.jface.action.ActionContributionItem.access$2(Act ionContributionItem.java:488)
>
> at
> org.eclipse.jface.action.ActionContributionItem$5.handleEven t(ActionContributionItem.java:400)
>
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :66)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1085)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:3180)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :2856)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1930)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1894)
> at
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Work bench.java:422)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.j ava:149)
> at
> org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplicatio n.java:95)
> at
> org.eclipse.core.internal.runtime.PlatformActivator$1.run(Pl atformActivator.java:78)
>
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .runApplication(EclipseAppLauncher.java:92)
>
> at
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher .start(EclipseAppLauncher.java:68)
>
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:400)
>
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:177)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336 )
> at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
> at org.eclipse.core.launcher.Main.run(Main.java:977)
> at org.eclipse.core.launcher.Main.main(Main.java:952)
>
>
>

Re: Can't create Java Run Configuration [message #249232 is a reply to message #249183]

Mon, 05 November 2007 04:33

Eclipse User

Originally posted by: jmason1966.hotmail.com

Thanks for the idea Eric ... don't think it was exactly that but it gave
me an idea and I have solved the issue ... by installing JRE 1.5 and using
that instead of Java 6

I'm still not sure what was happening ... but I assume Xerces was being
used somewhere by Eclipse and that was having trouble with Java 6. I
searched a lot of forums and found someone saying that. ... so as I tried
1.5 and bingo! can now create Run Configurations.

Still very vague about why this happened. On this system I've only ever
used Java 6 and everything used to be OK. Can only guess that something I
have updated its Xerces when I did a "Find and Install Updates" in
Eclipse. Also feel I'm making too many guesses ....

Re: Can't create Java Run Configuration [message #249281 is a reply to message #249232]

Mon, 05 November 2007 13:24

Eclipse User

Originally posted by: eclipse6.rizzoweb.com

JM wrote:
> Thanks for the idea Eric ... don't think it was exactly that but it gave
> me an idea and I have solved the issue ... by installing JRE 1.5 and
> using that instead of Java 6
>
> I'm still not sure what was happening ... but I assume Xerces was being
> used somewhere by Eclipse and that was having trouble with Java 6. I
> searched a lot of forums and found someone saying that. ... so as I
> tried 1.5 and bingo! can now create Run Configurations.
>
> Still very vague about why this happened. On this system I've only ever
> used Java 6 and everything used to be OK. Can only guess that something
> I have updated its Xerces when I did a "Find and Install Updates" in
> Eclipse. Also feel I'm making too many guesses ....

Eclipse does not include Xerces (or any other specific parser as far as
I know); it used to (long ago, in version 2.x or maybe earlier), but now
it just uses standard JAXP interfaces and relies on the XML parser that
is shipped with JDK 1.4 and above.
I'd bet a beverage or two that something had installed Xerces into the
/ext directory of your Java 6 installation.

Glad you up and running, in any case.

Eric

Previous Topic:	Howto create a new project wizard
Next Topic:	store project-specific information

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jun 28 23:28:27 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter