Folks, I don't know if this has been discussed before, but I ran into this issue the other day.
I am running Tomcat 4.1.18 on a Windows/2000 Pro machine as a service. Everything works well (integrated with Apache 2.0.43 or IIS 5 via mod_jk2). I was running j2sdk 1.4.1_01 and decided to do the minor upgrade to j2sdk 1.4.1_02. I knew there would be issues with several packages (Emacs jde, Sun 1 Studio 4 CE), and I managed to get those solved with only a little difficulty. Once I set my JAVA_HOME to the new directory and changed my PATH, I thought everything would be taken care of with Tomcat. Unfortunately, Tomcat would not start. Tomcat complained it could not find jvm.dll. I did some digging around in the batch files, and there was no mention of any hard-coded paths. I ended up backing up my custom configuration / applications, uninstalling Tomcat, and then re-installing Tomcat. Today I thought about investigating the registry. I found the following entry: HKEY_LOCAL_MACHINE-->ControlSet002-->Services--> Apache Tomcat 4.1-->Parameters-->JVM Library This was set to hard-coded path of jvm.dll. Of course, since I had installed Tomcat under the previous version of Java (1.4.1_01), the path no longer existed. I did this search after I had re-installed Tomcat, so I actually found the right path. However, rather than re-installing Tomcat, it appears that I could have changed the value of this entry to reflect the new location of jvm.dll and all would have been well. I hope this enables people to avoid problems and issues upgrading Java on Windows when running Tomcat as a service. /mde/ just my two cents . . . . __________________________________________________ Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! http://platinum.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
