Magnolia error to start by Tomcat - Something went wrong, version workspace for repository magnolia does not exist.

[Samuel Souza de Oliveira]

 Hello,

We are running Magnolia DX Core Version (bundle) 6.2.22 and we just updated the Java JDK version from 8 to 11, however, after the upgrade the application stopped to work, via browser it returns

HTTP Status 404 – Not Found
Type Status Report
Message Not found
Description The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.
Apache Tomcat/9.0.31

The Tomcat service is running but in logs I can see that the application could not be started, researching about that I found that Java JDK version is supported on Magnolia 6.2

https://docs.magnolia-cms.com/product-docs/6.2/Administration/Certified-stack.html

Any idea to identify why after the Java JDK upgrade the Magnolia application cannot be started by Tomcat?

Below, there is the logs found and in attach the full log trace.

Caused by: java.lang.RuntimeException: Something went wrong, version workspace for repository magnolia does not exist.
......

19:22:26.758 [main] DEBUG info.magnolia.context.AbstractRepositoryStrategy - releasing jcr sessions
19:22:26.761 [main] ERROR info.magnolia.init.MagnoliaServletContextListener - Oops, Magnolia could not be started
com.google.inject.CreationException: Unable to create injector, see the following errors:

1) Error injecting constructor, java.lang.RuntimeException: Something went wrong, version workspace for repository magnolia does not exist.
  at info.magnolia.cms.core.version.VersionManager.<init>(VersionManager.java:72)

......

25-Dec-2022 19:22:26.772 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
25-Dec-2022 19:22:26.776 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal Context [] startup failed due to previous errors
19:22:26.787 [main] INFO info.magnolia.repository.DefaultRepositoryManager - Shutting down JCR
19:22:26.787 [main] WARN info.magnolia.repository.WorkspaceMapping - Failed to retrieve repository provider 'magnolia'. Your Magnolia instance might not have been initialized properly

......

19:22:26.788 [main] DEBUG info.magnolia.context.AbstractRepositoryStrategy - releasing jcr sessions
25-Dec-2022 19:22:26.792 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [ROOT] registered the JDBC driver [com.mysql.cj.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

.....

25-Dec-2022 19:22:26.794 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [ROOT] appears to have started a thread named [Log4j2-AsyncAppenderEventDispatcher-1-log-activation] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:

.....

INFO [mysql-cj-abandoned-connection-cleanup] org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading Illegal access: this web application instance has been stopped already. Could not load []. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
        java.lang.IllegalStateException: Illegal access: this web application instance has been stopped already. Could not load []. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.   

[Samuli Saarinen]

I think the actual reason is missing from the logs. There are some exceptions about repository not existing but the reason for this is probably earlier in the startup.

BR, Samuli