Home » Language IDEs » Java Development Tools (JDT) » Can't run test in 3.0M7, WinXP due to java.io.IOException while creating process
| Can't run test in 3.0M7, WinXP due to java.io.IOException while creating process [message #145408] |
Wed, 25 February 2004 12:26  |
Eclipse User |
|
|
|
Originally posted by: seank.nulogy.com
I have a junit test that i cannot run or debug under Eclipse 3.0M7 that
previously worked under M6. When i try to run it, the following exception
shows up in the error log:
java.io.IOException: CreateProcess:
F:\java\j2sdk1.4.1_05\bin\javaw.exe -ea -Dcom.nulogy.interceptor.eventhandle
r=com.nulogy.ultimock.UltiMock "-Dcom.nulogy.interceptor.excludes=*Test,
*Suite, junit.*, org.eclipse.jdt.internal.junit.runner,
com.nulogy.ultimock.*, de.abstrakt.*,
Mock*" -Xbootclasspath/p:F:\temp\com.nulogy.ultimock_0.9.0\intercep tor.jar -
Xbootclasspath/a:F:\temp\com.nulogy.ultimock_0.9.0\asm.jar;F :\temp\com.nulog
y.ultimock_0.9.0\cglib-2.0-RC2.jar -classpath "/f:/eclipse
nulogy/plugins/org.eclipse.jdt.junit_3.0.0/junitsupport.jar; /f:/eclipse
nulogy/plugins/org.eclipse.jdt.junit.runtime_3.0.0/junitrunt ime.jar;F:\src\n
ulogy\clearbill\ui\test\bin;F:\src\nulogy\clearbill\ui\impl\ bin;F:\src\nulog
y\clearbill\core\impl\bin;F:\src\nulogy\util\impl\bin;F:\nul ogy
eclipse\plugins\org.dom4j_1.3.1\dom4j.jar;F:\nulogy
eclipse\plugins\org.eclipse.swt.win32_2.1.2\ws\win32\swt.jar ;F:\nulogy
eclipse\plugins\org.eclipse.ui_2.1.1\ui.jar;F:\nulogy
eclipse\plugins\org.eclipse.text_2.1.0\text.jar;F:\nulogy
eclipse\plugins\org.eclipse.jfac
|
|
|
| Re: Can't run test in 3.0M7, WinXP due to java.io.IOException while creating process [message #145660 is a reply to message #145408] |
Thu, 26 February 2004 04:00  |
| Eclipse User |
|
|
|
Originally posted by: daniel.megert.gmx.net
Sean Kirby wrote:
>I have a junit test that i cannot run or debug under Eclipse 3.0M7 that
>previously worked under M6. When i try to run it, the following exception
>shows up in the error log:
>
>
Looks like you're mixing 3.0 and 2.1 plug-ins.
>java.io.IOException: CreateProcess:
>F:\java\j2sdk1.4.1_05\bin\javaw.exe -ea -Dcom.nulogy.interceptor.eventhandle
>r=com.nulogy.ultimock.UltiMock "-Dcom.nulogy.interceptor.excludes=*Test,
>*Suite, junit.*, org.eclipse.jdt.internal.junit.runner,
>com.nulogy.ultimock.*, de.abstrakt.*,
>Mock*" -Xbootclasspath/p:F:\temp\com.nulogy.ultimock_0.9.0\intercep tor.jar -
> Xbootclasspath/a:F:\temp\com.nulogy.ultimock_0.9.0\asm.jar;F :\temp\com.nulog
>y.ultimock_0.9.0\cglib-2.0-RC2.jar -classpath "/f:/eclipse
> nulogy/plugins/org.eclipse.jdt.junit_3.0.0/junitsupport.jar; /f:/eclipse
> nulogy/plugins/org.eclipse.jdt.junit.runtime_3.0.0/junitrunt ime.jar;F:\src\n
> ulogy\clearbill\ui\test\bin;F:\src\nulogy\clearbill\ui\impl\ bin;F:\src\nulog
> y\clearbill\core\impl\bin;F:\src\nulogy\util\impl\bin;F:\nul ogy
>eclipse\plugins\org.dom4j_1.3.1\dom4j.jar;F:\nulogy
> eclipse\plugins\org.eclipse.swt.win32_2.1.2\ws\win32\swt.jar ;F:\nulogy
>eclipse\plugins\org.eclipse.ui_2.1.1\ui.jar;F:\nulogy
>eclipse\plugins\org.eclipse.text_2.1.0\text.jar;F:\nulogy
>eclipse\plugins\org.eclipse.jfac”
>at java.lang.Win32Process.create(Native Method)
>at java.lang.Win32Process.<init>(Win32Process.java:67)
>at java.lang.Runtime.execInternal(Native Method)
>at java.lang.Runtime.exec(Runtime.java:566)
>at org.eclipse.debug.core.DebugPlugin.exec(DebugPlugin.java:571 )
>at org.eclipse.jdt.launching.AbstractVMRunner.exec(AbstractVMRu nner.java:70)
>at
> org.eclipse.jdt.internal.launching.StandardVMRunner.run(Stan dardVMRunner.jav
>a:241)
>at
> org.eclipse.jdt.internal.junit.launcher.JUnitBaseLaunchConfi guration.launch(
>JUnitBaseLaunchConfiguration.java:77)
>at
> org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfigurati
>on.java:157)
>at
> org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlugin.jav
>a:778)
>at org.eclipse.debug.ui.DebugUITools.buildAndLaunch(DebugUITool s.java:628)
>at org.eclipse.debug.ui.DebugUITools$3.run(DebugUITools.java:58 4)
>at org.eclipse.core.internal.jobs.Worker.run(Worker.java:62)
>
>One observation that i have made is that the first line of the exception
>trace is always the same length (1045 characters not including the "”"). I
>don't know if this is because of a limitation in the exception trace or if
>it is the actual problem.
>
>Any ideas? Thanks in advance,
>
>Sean Kirby
>
>
>
>
|
|
|
| Re: Can't run test in 3.0M7, WinXP due to java.io.IOException while creating process [message #145918 is a reply to message #145660] |
Thu, 26 February 2004 21:56 |
| Eclipse User |
|
|
|
Originally posted by: seank.nulogy.com
Yeah, i'm using M7 to launch plugins that run on Eclipse 2.1. Is that a
problem? I used to be able to do exactly what i'm doing in M7 on M6. I
think that this is a bug, but perhaps launching run-time workbenches based
on pre-3.0 versions of Eclipse isn't being supported anymore. Is this true?
Thanks for the response,
Sean
"Daniel Megert" <daniel.megert@gmx.net> wrote in message
news:c1kcdh$5o0$1@eclipse.org...
> Sean Kirby wrote:
>
> >I have a junit test that i cannot run or debug under Eclipse 3.0M7 that
> >previously worked under M6. When i try to run it, the following
exception
> >shows up in the error log:
> >
> >
> Looks like you're mixing 3.0 and 2.1 plug-ins.
>
> >java.io.IOException: CreateProcess:
>
>F:\java\j2sdk1.4.1_05\bin\javaw.exe -ea -Dcom.nulogy.interceptor.eventhandl
e
> >r=com.nulogy.ultimock.UltiMock "-Dcom.nulogy.interceptor.excludes=*Test,
> >*Suite, junit.*, org.eclipse.jdt.internal.junit.runner,
> >com.nulogy.ultimock.*, de.abstrakt.*,
>
>Mock*" -Xbootclasspath/p:F:\temp\com.nulogy.ultimock_0.9.0\intercep tor.jar
-
>
> Xbootclasspath/a:F:\temp\com.nulogy.ultimock_0.9.0\asm.jar;F :\temp\com.nulo
g
> >y.ultimock_0.9.0\cglib-2.0-RC2.jar -classpath "/f:/eclipse
> > nulogy/plugins/org.eclipse.jdt.junit_3.0.0/junitsupport.jar; /f:/eclipse
>
> nulogy/plugins/org.eclipse.jdt.junit.runtime_3.0.0/junitrunt ime.jar;F:\src\
n
>
> ulogy\clearbill\ui\test\bin;F:\src\nulogy\clearbill\ui\impl\ bin;F:\src\nulo
g
> > y\clearbill\core\impl\bin;F:\src\nulogy\util\impl\bin;F:\nul ogy
> >eclipse\plugins\org.dom4j_1.3.1\dom4j.jar;F:\nulogy
> > eclipse\plugins\org.eclipse.swt.win32_2.1.2\ws\win32\swt.jar ;F:\nulogy
> >eclipse\plugins\org.eclipse.ui_2.1.1\ui.jar;F:\nulogy
> >eclipse\plugins\org.eclipse.text_2.1.0\text.jar;F:\nulogy
> >eclipse\plugins\org.eclipse.jfac
|
|
|
| Re: Can't run test in 3.0M7, WinXP due to java.io.IOException while creating process [message #149999 is a reply to message #145918] |
Sat, 20 March 2004 14:13 |
| Eclipse User |
|
|
|
Originally posted by: daniel.megert.gmx.net
Sean Kirby wrote:
>Yeah, i'm using M7 to launch plugins that run on Eclipse 2.1. Is that a
>problem? I used to be able to do exactly what i'm doing in M7 on M6. I
>think that this is a bug, but perhaps launching run-time workbenches based
>on pre-3.0 versions of Eclipse isn't being supported anymore. Is this true?
>
>
The problem happens when you don't have all needed plug-ins in your
workspace and when your launch config uses the external plug-ins. This
results in a mix which causes the error.
Dani
>Thanks for the response,
>
>Sean
>
>"Daniel Megert" <daniel.megert@gmx.net> wrote in message
>news:c1kcdh$5o0$1@eclipse.org...
>
>
>>Sean Kirby wrote:
>>
>>
>>
>>>I have a junit test that i cannot run or debug under Eclipse 3.0M7 that
>>>previously worked under M6. When i try to run it, the following
>>>
>>>
>exception
>
>
>>>shows up in the error log:
>>>
>>>
>>>
>>>
>>Looks like you're mixing 3.0 and 2.1 plug-ins.
>>
>>
>>
>>>java.io.IOException: CreateProcess:
>>>
>>>
>>F:\java\j2sdk1.4.1_05\bin\javaw.exe -ea -Dcom.nulogy.interceptor.eventhandl
>>
>>
>e
>
>
>>>r=com.nulogy.ultimock.UltiMock "-Dcom.nulogy.interceptor.excludes=*Test,
>>>*Suite, junit.*, org.eclipse.jdt.internal.junit.runner,
>>>com.nulogy.ultimock.*, de.abstrakt.*,
>>>
>>>
>>Mock*" -Xbootclasspath/p:F:\temp\com.nulogy.ultimock_0.9.0\intercep tor.jar
>>
>>
>-
>
>
>> Xbootclasspath/a:F:\temp\com.nulogy.ultimock_0.9.0\asm.jar;F :\temp\com.nulo
>>
>>
>g
>
>
>>>y.ultimock_0.9.0\cglib-2.0-RC2.jar -classpath "/f:/eclipse
>>> nulogy/plugins/org.eclipse.jdt.junit_3.0.0/junitsupport.jar; /f:/eclipse
>>>
>>>
>> nulogy/plugins/org.eclipse.jdt.junit.runtime_3.0.0/junitrunt ime.jar;F:\src\
>>
>>
>n
>
>
>> ulogy\clearbill\ui\test\bin;F:\src\nulogy\clearbill\ui\impl\ bin;F:\src\nulo
>>
>>
>g
>
>
>>> y\clearbill\core\impl\bin;F:\src\nulogy\util\impl\bin;F:\nul ogy
>>>eclipse\plugins\org.dom4j_1.3.1\dom4j.jar;F:\nulogy
>>> eclipse\plugins\org.eclipse.swt.win32_2.1.2\ws\win32\swt.jar ;F:\nulogy
>>>eclipse\plugins\org.eclipse.ui_2.1.1\ui.jar;F:\nulogy
>>>eclipse\plugins\org.eclipse.text_2.1.0\text.jar;F:\nulogy
>>>eclipse\plugins\org.eclipse.jfac”
>>>at java.lang.Win32Process.create(Native Method)
>>>at java.lang.Win32Process.<init>(Win32Process.java:67)
>>>at java.lang.Runtime.execInternal(Native Method)
>>>at java.lang.Runtime.exec(Runtime.java:566)
>>>at org.eclipse.debug.core.DebugPlugin.exec(DebugPlugin.java:571 )
>>>at
>>>
>>>
> org.eclipse.jdt.launching.AbstractVMRunner.exec(AbstractVMRu nner.java:70)
>
>
>>>at
>>>
>>>
>> org.eclipse.jdt.internal.launching.StandardVMRunner.run(Stan dardVMRunner.ja
>>
>>
>v
>
>
>>>a:241)
>>>at
>>>
>>>
>> org.eclipse.jdt.internal.junit.launcher.JUnitBaseLaunchConfi guration.launch
>>
>>
>(
>
>
>>>JUnitBaseLaunchConfiguration.java:77)
>>>at
>>>
>>>
>> org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfigurat
>>
>>
>i
>
>
>>>on.java:157)
>>>at
>>>
>>>
>> org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlugin.ja
>>
>>
>v
>
>
>>>a:778)
>>>at
>>>
>>>
> org.eclipse.debug.ui.DebugUITools.buildAndLaunch(DebugUITool s.java:628)
>
>
>>>at org.eclipse.debug.ui.DebugUITools$3.run(DebugUITools.java:58 4)
>>>at org.eclipse.core.internal.jobs.Worker.run(Worker.java:62)
>>>
>>>One observation that i have made is that the first line of the exception
>>>trace is always the same length (1045 characters not including the "”").
>>>
>>>
>I
>
>
>>>don't know if this is because of a limitation in the exception trace or
>>>
>>>
>if
>
>
>>>it is the actual problem.
>>>
>>>Any ideas? Thanks in advance,
>>>
>>>Sean Kirby
>>>
>>>
>>>
>>>
>>>
>>>
>
>
>
>
|
|
|
| Re: Can't run test in 3.0M7, WinXP due to java.io.IOException while creating process [message #150214 is a reply to message #149999] |
Tue, 23 March 2004 05:15 |
| Eclipse User |
|
|
|
Sean,
Having a similar problem, I investigated and found out that there is a big
difference between M6 and M7 for generated command line which can be the
origin of your problem. I introduced a bug for it see Bug 55638.
Greetings
Jacques
Daniel Megert wrote:
> Sean Kirby wrote:
> >Yeah, i'm using M7 to launch plugins that run on Eclipse 2.1. Is that a
> >problem? I used to be able to do exactly what i'm doing in M7 on M6. I
> >think that this is a bug, but perhaps launching run-time workbenches based
> >on pre-3.0 versions of Eclipse isn't being supported anymore. Is this true?
> >
> >
> The problem happens when you don't have all needed plug-ins in your
> workspace and when your launch config uses the external plug-ins. This
> results in a mix which causes the error.
> Dani
> >Thanks for the response,
> >
> >Sean
> >
> >"Daniel Megert" <daniel.megert@gmx.net> wrote in message
> >news:c1kcdh$5o0$1@eclipse.org...
> >
> >
> >>Sean Kirby wrote:
> >>
> >>
> >>
> >>>I have a junit test that i cannot run or debug under Eclipse 3.0M7 that
> >>>previously worked under M6. When i try to run it, the following
> >>>
> >>>
> >exception
> >
> >
> >>>shows up in the error log:
> >>>
> >>>
> >>>
> >>>
> >>Looks like you're mixing 3.0 and 2.1 plug-ins.
> >>
> >>
> >>
> >>>java.io.IOException: CreateProcess:
> >>>
> >>>
> >>F:javaj2sdk1.4.1_05binjavaw.exe -ea -Dcom.nulogy.interceptor.eventhandl
> >>
> >>
> >e
> >
> >
> >>>r=com.nulogy.ultimock.UltiMock "-Dcom.nulogy.interceptor.excludes=*Test,
> >>>*Suite, junit.*, org.eclipse.jdt.internal.junit.runner,
> >>>com.nulogy.ultimock.*, de.abstrakt.*,
> >>>
> >>>
> >>Mock*" -Xbootclasspath/p:F:tempcom.nulogy.ultimock_0.9.0interceptor .jar
> >>
> >>
> >-
> >
> >
> >> Xbootclasspath/a:F:tempcom.nulogy.ultimock_0.9.0asm.jar;F:te mpcom.nulo
> >>
> >>
> >g
> >
> >
> >>>y.ultimock_0.9.0cglib-2.0-RC2.jar -classpath "/f:/eclipse
> >>> nulogy/plugins/org.eclipse.jdt.junit_3.0.0/junitsupport.jar; /f:/eclipse
> >>>
> >>>
> >> nulogy/plugins/org.eclipse.jdt.junit.runtime_3.0.0/junitrunt ime.jar;F:src
> >>
> >>
> >n
> >
> >
> >> ulogyclearbilluitestbin;F:srcnulogyclearbilluiimplbin;F:srcn ulo
> >>
> >>
> >g
> >
> >
> >>>yclearbillcoreimplbin;F:srcnulogyutilimplbin;F:nulogy
> >>>eclipsepluginsorg.dom4j_1.3.1dom4j.jar;F:nulogy
> >>> eclipsepluginsorg.eclipse.swt.win32_2.1.2wswin32swt.jar;F:nu logy
> >>>eclipsepluginsorg.eclipse.ui_2.1.1ui.jar;F:nulogy
> >>>eclipsepluginsorg.eclipse.text_2.1.0text.jar;F:nulogy
> >>>eclipsepluginsorg.eclipse.jfac
> >>>at java.lang.Win32Process.create(Native Method)
> >>>at java.lang.Win32Process.<init>(Win32Process.java:67)
> >>>at java.lang.Runtime.execInternal(Native Method)
> >>>at java.lang.Runtime.exec(Runtime.java:566)
> >>>at org.eclipse.debug.core.DebugPlugin.exec(DebugPlugin.java:571 )
> >>>at
> >>>
> >>>
> > org.eclipse.jdt.launching.AbstractVMRunner.exec(AbstractVMRu nner.java:70)
> >
> >
> >>>at
> >>>
> >>>
> >> org.eclipse.jdt.internal.launching.StandardVMRunner.run(Stan dardVMRunner.ja
> >>
> >>
> >v
> >
> >
> >>>a:241)
> >>>at
> >>>
> >>>
> >> org.eclipse.jdt.internal.junit.launcher.JUnitBaseLaunchConfi guration.launch
> >>
> >>
> >(
> >
> >
> >>>JUnitBaseLaunchConfiguration.java:77)
> >>>at
> >>>
> >>>
> >> org.eclipse.debug.internal.core.LaunchConfiguration.launch(L aunchConfigurat
> >>
> >>
> >i
> >
> >
> >>>on.java:157)
> >>>at
> >>>
> >>>
> >> org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(D ebugUIPlugin.ja
> >>
> >>
> >v
> >
> >
> >>>a:778)
> >>>at
> >>>
> >>>
> > org.eclipse.debug.ui.DebugUITools.buildAndLaunch(DebugUITool s.java:628)
> >
> >
> >>>at org.eclipse.debug.ui.DebugUITools$3.run(DebugUITools.java:58 4)
> >>>at org.eclipse.core.internal.jobs.Worker.run(Worker.java:62)
> >>>
> >>>One observation that i have made is that the first line of the exception
> >>>trace is always the same length (1045 characters not including the "").
> >>>
> >>>
> >I
> >
> >
> >>>don't know if this is because of a limitation in the exception trace or
> >>>
> >>>
> >if
> >
> >
> >>>it is the actual problem.
> >>>
> >>>Any ideas? Thanks in advance,
> >>>
> >>>Sean Kirby
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >
> >
> >
> >
|
|
|
Goto Forum:
Current Time: Fri Jul 18 23:30:42 EDT 2025
Powered by FUDForum. Page generated in 0.04002 seconds |
Home