BlackRose01 / docker-openolat

Create a Dockerimage for OpenOlat
4 stars 8 forks source link

Severe Crash (possibly due to missing JAVA/CATALINA options) #3

Open SavSanta opened 4 years ago

SavSanta commented 4 years ago

Cant get this docker image to run

I basically get a similiar abandoned and then exception as is mentioned in the other issue.

WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release Nov 21, 2020 4:09:30 PM org.apache.catalina.core.StandardContext startInternal SEVERE: One or more listeners failed to start. Full details will be found in the appropriate container log file Nov 21, 2020 4:09:30 PM org.apache.catalina.core.StandardContext startInternal SEVERE: Context [] startup failed due to previous errors Nov 21, 2020 4:09:30 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesJdbc WARNING: The web application [ROOT] registered the JDBC driver [org.postgresql.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered. Nov 21, 2020 4:09:30 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesJdbc WARNING: The web application [ROOT] registered the JDBC driver [com.mysql.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. Nov 21, 2020 4:09:30 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesJdbc WARNING: The web application [ROOT] registered the JDBC driver [com.mysql.fabric.jdbc.FabricMySQLDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered. Nov 21, 2020 4:09:30 PM org.apache.catalina.loader.WebappClassLoaderBase clearReferencesThreads WARNING: The web application [ROOT] appears to have started a thread named [Abandoned connection cleanup thread] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread: java.base@11.0.9/java.lang.Object.wait(Native Method) java.base@11.0.9/java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:155) com.mysql.jdbc.AbandonedConnectionCleanupThread.run(AbandonedConnectionCleanupThread.java:64) java.base@11.0.9/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) java.base@11.0.9/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) java.base@11.0.9/java.lang.Thread.run(Thread.java:834) Nov 21, 2020 4:09:30 PM org.apache.catalina.startup.HostConfig deployDescriptor INFO: Deployment of deployment descriptor [/opt/openolat/conf/Catalina/localhost/ROOT.xml] has finished in [18,138] ms Nov 21, 2020 4:09:30 PM org.apache.coyote.AbstractProtocol start INFO: Starting ProtocolHandler ["http-nio-8088"] Nov 21, 2020 4:09:30 PM org.apache.catalina.startup.Catalina start INFO: Server startup in [18247] milliseconds Nov 21, 2020 4:09:34 PM org.apache.catalina.loader.WebappClassLoaderBase checkStateForResourceLoading INFO: 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. at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading(WebappClassLoaderBase.java:1385) at org.apache.catalina.loader.WebappClassLoaderBase.getResource(WebappClassLoaderBase.java:1038) at com.mysql.jdbc.AbandonedConnectionCleanupThread.checkContextClassLoaders(AbandonedConnectionCleanupThread.java:90) at com.mysql.jdbc.AbandonedConnectionCleanupThread.run(AbandonedConnectionCleanupThread.java:63) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834)

I though the issue was it running out of memory so I used the really confusing and not to helpful official openOLAT installation documentation and see this page mentions that it may need the CATALINA_OPTS variable passed with certain limits. So i tried a few different ways to edit the setenv and exported variables to pass -Xmx1024m -Xms512m -XX:MaxMetaspaceSize=512m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=. . That didnt have an effect. Java itself is pretty confusing between the environment variables so maybe it's suppose to be JAVA_OPTS or JRE_OPTS or something different but I wouldnt know.

Any ideas welcome! Though, to be honest I wanted to evaluate openOLAT but it really is quite tricky to get it to run so maybe I wont submit it for our organization. Though, I'd like to help in solving for the future users