DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=41538>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=41538 ------- Additional Comments From [EMAIL PROTECTED] 2007-02-08 03:53 ------- I had the exact same issue on a W2K3 server running 5.5.20 (due to a tester installing JDK1.6 by mistake instead of JDK1.5 since it is now the default JDK choice on Sun web site). I was on a urge for a "CEO" demo, and did not investigate much (and went back to JDK 1.5), but it seems to be related to configuration of tomcat windows service using jvm.dll and some changes in JDK1.6 related to usage of jvm.dll from a windows service (PATH related ?) So the problem is very likely tomcat windows service installer when using jdk1.6. I guess that if one does the following steps, he can easily reproduce the issue: - install a clean W2K3 server OS : no previous JDK or tomcat installation or environment variable changes like PATH or JAVA_HOME - install JDK1.6 (and JRE 1.6 inside JDK setup) - install tomcat 5.5.20 as a windows service - start the tomcat service I really think this is a "blocker" issue as it simply prevents running tomcat as a service on some installations with current recommended JDK/JRE versions (1.6). I should be kept open until tomcat service installation works with JDK1.6 on clean servers or at least a documented work-around is found for those installations. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
