This was fixed by adding "--add-opens=java.base/java.lang=ALL-UNNAMED". Now
all applications are running, and various other issues have been fixed by
other "--add-opens" arguments. So these and the last couple of issues are
related to Java 17 and not the classloader code above.
Can a Tomcat expert
The security manager is deprecated in newer versions of Java. If you are
new to Tomcat, whatever problem using the security manager is intended
to solve, I'd strongly encourage you to find an alternative solution.
The codebase refers to the JAR trying to read the file, not the file the
JAR is
Hello,
I'm very new to tomcat, forgive me if I did not found my answer
elsewhere, i'm currently out of of ideas.
I'm trying to setup a standalone tomcat9 (9.0.31-1~deb10u7) on Debian
11, with security manager enabled.
I'm seeing in catalina logs the following stacktrace (full stacktrace
pr
The information you posted is missing line breaks and is extremely
difficult to parse. Please re-post with line breaks.
Mark
On 21/12/2022 08:02, alik alikov wrote:
Main lundagrossisten site lundagrossisten.se web application 1 0client-error-logging-servlet com.gridnine.platform.server
Main
lundagrossisten site lundagrossisten.se web
application 1
0
client-error-logging-servlet
com.gridnine.platform.server.lundase.web.servlet.ClientErrorLoggingServlet
client-error-logging-servlet
/client-error/*
warehouses-servlet
com.gridnine.platform.server.lundase.web.ser