This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
java.io.IOException: CreateProcess: C:\jdk1.4.1\jre\..\bin\java -classpath "C:\Program Files\s1studio\ce\tomcat401\bin\bootstrap.jar;C:\jdk1.4.1\jre\..\lib\tools.jar" "-Dcatalina.home=C:\Program Files\s1studio\ce\tomcat401" "-Dcatalina.base=C:\Program Files\s1studio\ide-userdir\tomcat401_base" org.apache.catalina.startup.Bootstrap start error=193 at java.lang.Win32Process.create(Native Method) at java.lang.Win32Process.<init>(Win32Process.java:63) at java.lang.Runtime.execInternal(Native Method) at java.lang.Runtime.exec(Runtime.java:550) at java.lang.Runtime.exec(Runtime.java:475) at java.lang.Runtime.exec(Runtime.java:441) at org.openide.execution.NbProcessDescriptor.exec(NbProcessDescriptor.java:229) at org.openide.execution.NbProcessDescriptor.exec(NbProcessDescriptor.java:132) at org.openide.execution.NbProcessDescriptor.exec(NbProcessDescriptor.java:293) at org.openide.execution.NbProcessDescriptor.exec(NbProcessDescriptor.java:304) at org.netbeans.modules.tomcat.tomcat40.Tomcat40Installation.createNewTomcatProcess(Tomcat40Installation.java:1120) at ... it is possible that sometimes the command that starts Tomcat is too long and causes this problem (reinstalling to something like C:\Tomcat should help) as Riyad pointed out.
To follow this up, on the following machines I've noticed this problem: Windows XP (SP1) Tomcat 4.1.24 JDK 1.4.1_02 NetBeans 3.5 AND Windows Server 2003 Tomcat 4.1.24 JDK 1.4.1_02 NetBeans 3.5 I would allow Tomcat to install to the default location (C:\Program Files\Apache Group\Tomcat 4.1) and then I would add an additional server to the runtime tab in the IDE, under the server node to point to that installation of Tomcat. When I would go to launch my web application, I would never be able to get past the IOException described below. As I mentioned in the news groups, I would see something LIKE this: C:\jdk1.4.1\jre\..\bin\java -classpath "C:\Program Files\Apache Group\Tomcat 4.1\common\servlet.jar;<... about 13 more jars">;C:\Program Files\Apache Gr and the end of the string would be concatonated like that. My first guess was that the execution string was just too long and ran out of enough (environment) space, so it got cut. I solved this problem both times by reinstalling tomcat into the directory "C:\Tomcat". If this is an environment space issue, then its definately not netbean's problem, but you might want to issue a popup when a user sets the working dir of the external servlet container installation if its too long. PLEASE NOTE: When I first had this problem, I reinstalled Tomcat in "C:\Tomcat 4.1" and it still did not work, even though I shaved off about 20 characters from the path. The execution string still got concatonated, so I am still not totally sold that the problem is the length of the dir, because even when I shortended it, it still didn't work. Can this be investigated to see if its a space-in-the-path issue? I think a good test case would be to install Tomcat 4.1.24 into 4 different directories: C:\Tomcat (Shortest) C:\Tomcat_4.1 (Same length as next one, but no space) C:\Tomcat 4.1 (Failed short one) C:\Program Files\Apache Group\Tomcat 4.1 (Default) And install all the servers and try and launch a web application with each one. NOTE: The web application I was attempting to use was a straight JSP/Servlet; no custom tags, no struts, nothing.
*** This issue has been marked as a duplicate of 29625 ***