The most likely cause of this is that you have outdated entries for your
JRE
/ JDK in your Windows registry.
Thanks for the suggestion, but this is a clean install of JDK1.3.1! Any
other ideas?
- Original Message -
From: Remy Maucherat [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent:
I've fixed the problem myself. I had to modify (only slightly) the scripts
supplied with JavaService 1.2.0, by specifying the current directory from
which to launch Tomcat 4.0. See the modified version below (sorry for any
line breaks...).
-Chris
@echo off
echo
echo Usage: %0
It's not a patch for Tomcat, it's an update for an example script for a
third-party tool (a very good one, not just for tomcat).
I don't think there are any portability issues really, as it's not concerned
with web applications directly, it's more to do with how the servlet engine
is launched,
Hello,
I've installed previous beta versions of Tomcat 4 as an NT service using the
JavaService tool from
http://www.alexandriasc.com/software/JavaService/index.html without problem.
I tried the same thing using RC1, but Tomcat wouldn't start. Here's the
exception that appeared on STDOUT :
Hello,
I've installed previous beta versions of Tomcat 4 as an NT service using
the
JavaService tool from
http://www.alexandriasc.com/software/JavaService/index.html without
problem.
I tried the same thing using RC1, but Tomcat wouldn't start. Here's the
exception that appeared on STDOUT