Nathan, I ran into this problem when Tomcat was trying to use a diff JVM then the one I specified in JAVA_HOME. I had a JRE installed at one point, then later installed the SDK. Tomcat was using the sdk as it's JAVA_HOME, but was getting confused and pointing to the JRE from the first install.
In the Registry, go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Apache Tomcat 4.1\Parameters Check the value of JVM Library - and make sure it is pointing to JAVA_HOME\jre\bin\client\jvm.dll Where java_home is the java_home that Tomcat picked during it's Installer process. Hope this helps. -----Original Message----- From: Nathan McMinn [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 02, 2003 10:06 AM To: Tomcat Users List Subject: Re: repost: JSP Compile Fails There are no spaces. The system runs on win2k, and the install path for tomcat is d:\tomcat418. I don;'t think this is a problem related to ant bug 10499 (spaces in install path), I think it is something different. It appears as though the classpath ant is trying to use is simply too long. ----- Original Message ----- From: "Tom Cole" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Wednesday, July 02, 2003 8:44 AM Subject: Re: repost: JSP Compile Fails > Spaces in your install path for Tomcat will cause ANT to fail. You > should reinstall with a new path that does not include spaces. > > ----- Original Message ----- > From: "Nathan McMinn" <[EMAIL PROTECTED]> > To: "Tomcat Users List" <[EMAIL PROTECTED]> > Sent: Wednesday, July 02, 2003 9:41 AM > Subject: repost: JSP Compile Fails > > > I recently upgraded to tomcat 4.1.24 from 4.1.18. After performing > this upgrade, whenever I try to deploy a new version of a JSP page on > the server, > the compile fails. I have tracked this down to this bit of the stack trace: > > Caused by: java.io.IOException: CreateProcess: javac.exe -classpath > D:\Tomcat418\bin\bootstrap.jar;D:\Tomcat418\webapps\wwxchange\WEB-INF\lib\Li > nearBarCode.jar;D:\Tomcat418\webapps\wwxchange\WEB-INF\lib\WWXchange.jar;D:\ > Tomcat418\shared\classes;D:\Tomcat418\common\classes;D:\Tomcat418\common\lib > \activation.jar;D:\Tomcat418\common\lib\ant.jar;D:\Tomcat418\common\lib\comm > ons-collections.jar;D:\Tomcat418\common\lib\commons-dbcp.jar;D:\Tomcat418\co > mmon\lib\commons-httpclient-2.0-beta1.jar;D:\Tomcat418\common\lib\commons-lo > gging-api.jar;D:\Tomcat418\common\lib\commons-logging.jar;D:\Tomcat418\commo > n\lib\commons-pool.jar;D:\Tomcat418\common\lib\Commons.jar;D:\Tomcat418\comm > on\lib\EJOB.jar;D:\Tomcat418\common\lib\ftpbean.jar;D:\Tomcat418\common\lib\ > jakarta-poi-1.10.0-dev-20030222.jar;D:\Tomcat418\common\lib\jasper-compiler. > jar;D:\Tomcat418\common\lib\jasper-runtime.jar;D:\Tomcat418\common\lib\mail. > jar;D:\Tomcat418\common\lib\mm.mysql-2.0.14-bin.jar;D:\Tomcat418\common\lib\ > naming-common.jar;D:\Tomcat418\common\lib\naming-factory.jar;D:\Tomcat418\co > ? > > It seems like ant is truncating the classpath. Does this need to be posted > to the ant mailing list? If not, the only workaround I can find is to > unpack jars to the common/classes directory, thus shortening the classpath. > Does anybody know a "cleaner" way to handle this? > > --Nathan McMinn > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
