Nothing you mentioned could have any effect.
How do you ensure jdks are not mixing between tomcat and the other jdk8
application?
Try to use separated cmd files as described above for both Tomcat and the
other application and remove all jdk configurations from windows variables
just to test this
There isn't any sign of the tomcat restart in the tomcat logs. In
tomcat9-stderr-2022-04-08.log there is just one bootstrap section with the path
to JDK 17, followed by mesages about the registering webapps. Then weekend of
silence interrupted by today's exception.
In that bootstrap section
Hi Jan,
looks like somebody/something has restarted tomcat with different
JAVA_HOME/PATH variables. It is not possible to change jvm process while
running.
Another option could be you have there running two tomcat instances.
Create cmd file e.g. tomcatStart.cmd with content like
set
We have a mixed JDK environment on our internal Windows Server.
Tomcat is installed using the service installer and its service
configuration points to the JDK 17 as it serves some internal apps requiring
JDK 12+.
JAVA_HOME points to older JDK 8.
PATH variable contains link to JDK 8, but
Hi Chris
Thank you for the information, this is interesting indeed.
Yes, I am using the default service installed by Tomcat installer so using
procrun and tomcat9.exe
I have tried adding -DCATALINA_OPTS="-Xms20g -Xmx20g" under the Java Options
parameters in tomcat9w.exe > Java tab
But this is