trouble starting tomcat: "error 0" on Windows 64bit

2009-05-15 Thread w...@serensoft.com
We're having a heck of a time getting tomcat running on windows server 2003 enterprise x64 -- it barely gets started, and instantly quits. We installed java from jdk-1_5_0_18-windows-amd64.exe which seems to be the only 64-bit version available? Our processor is intel, tho... Is there an intel-not

Re: trouble starting tomcat: "error 0" on Windows 64bit

2009-05-16 Thread w...@serensoft.com
taller (jdk-1_5_0_18-windows-amd64.exe) so in theory they should be compatible, no? >> Date: Sat, 16 May 2009 00:17:39 -0500 >> Subject: trouble starting tomcat: "error 0" on Windows 64bit >> From: w...@serensoft.com >> To: users@tomcat.apache.org >> >> We&

startup.bat and catalina.bat -> NoClassDefFoundError: server

2009-05-16 Thread w...@serensoft.com
First, I appreciate your responses and your help. Thanks! Here's my new question: Short version: We find what the launch-tomcat command is from the startup.bat and catalina.bat files, and paste that in directly at the command line, only to get: "Exception in thread "main" java.lang.NoClassDefFoun

running tomcat5 -- as a service under 64-bit windows?

2009-05-18 Thread w...@serensoft.com
Hi folks -- Short version: how to get Tomcat5 to run as a service under 64-bit Windows 2003? Long version: Okay, we've got Tomcat5 running from the command-line within 64-bit Windows 2003 Enterprise (and cannot use tomcat 6/java 6 for our project) -- and now we're working to get it running as a

never mind :)

2009-05-18 Thread w...@serensoft.com
We just got Tomcat 5 to work as a service on windows 64-bit, woo hoo! (see email with subject "running tomcat5 -- as a service under 64-bit windows? SOLVED".) We thought we had another new snag, but there's just a firewall or network issue. We now return you to your regularly scheduled email. :)

"The Apache Tomcat service terminated with service-specific error 0 (0x0)." on Windows again... argh!

2009-06-06 Thread w...@serensoft.com
Okay -- wWe CAN start Tomcat via the command line, no problem. But when trying to start it as a SERVICE, no luck -- we look in the event logs and find "The Apache Tomcat service terminated with service-specific error 0 (0x0)." again In JAVA_OPTS we've got "-server -XX:+UseParallelGC -Xmx1200m -XX