You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/10/30 19:23:20 UTC
DO NOT REPLY [Bug 14097] New: -
hardcoded registry value for vm lets tomcat service on win2k fail
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14097>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=14097
hardcoded registry value for vm lets tomcat service on win2k fail
Summary: hardcoded registry value for vm lets tomcat service on
win2k fail
Product: Tomcat 4
Version: 4.1.10
Platform: PC
OS/Version: MacOS 9
Status: NEW
Severity: Enhancement
Priority: Other
Component: Catalina
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: lh@tpso.com
Hi,
the registry entry HKLM\System\CurrentControlSet\Services\Apache Tomcat 4.1
\Parameters\JVM Library hardcodes the path to the VM. When one changes the
installed JDK/JRE (and thus usually has a new JAVA_HOME dir), the service won't
start anymore.
As the flexibility gained by once defining JAVA_HOME as an environment variable
is so nice, i would suggest not to hardcode this parameter and instead use the
environment variable value. the documentation should be upgraded as well to
inform win2k/xp-users they shall define JAVA_HOME as system, not user variable.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>