Am 22.01.2016 um 14:29 schrieb David kerber:
On 1/22/2016 8:06 AM, Christoph P.U. Kukulies wrote:
Windows 7:

Today I installed Java 8 on my windows 7 machine and did an upgrade of
the CMS at the same time (from OpenCMS 9.5.2 to 9.5.3).
After the Java update and the CMS update suddenly my tomcat 6.0.39
didn't start any longer. The service gave an error at start time:

Der Dienst "Apache Tomcat 6.0 Tomcat6" wurde mit folgendem
dienstspezifischem Fehler beendet: Unzulässige Funktion..

My thoughts came to tomcat6 possibly not being compatible with Java8 and
so I decided to install tomcat 7.0 which started fine.

When starting my CMS system again I now found that it did some
unpleasant things for which I wanted to rule out tomcat7 being the culprit and switch the jvm.dll in the tomcat7 configurator to the jre1.7 jvm.dll.

Then suddenly I got the same error as under tomcat6.0 when I tried to
start tomcat7 again.

Could it be that the Java8 installer screws the existing Java 7 ? Or
does it change some global parameters that tomcat reads at start time.

If you take the default installation location and do not allow it to remove the old one, Java 8 will not alter your java 7 installation.

However, which java is found if you do not explicitly specify which one to run, may change. Try dropping to a command prompt, and type

java -version

That will tell you which one is the default. If your app needs a different one, you will have to specify it.

Thanks. Java -version gives

U:\>java -version
java version "1.8.0_71"
Java(TM) SE Runtime Environment (build 1.8.0_71-b15)
Java HotSpot(TM) 64-Bit Server VM (build 25.71-b15, mixed mode)

So could tomcat6 been puzzled by this? The tomcat6 configurator had most probably the 7.0 jvm configured, wouldn't it? Since the java 8 installer would not mess with tomcat6 configuration. Iin other words: can I conclude that the java8 update (which preserved
java7) cannot be the reason why tomcat6 didn't start.


To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to