I've researched similar questions on different forums and StackOverflow, but none of the solutions offered worked for me. I'm using the entrypoint.sh with js-docker and JasperServer Community Edition. The issue is that Tomcat outputs
INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory /usr/local/tomcat/webapps/jasperserver
and after several seconds, also
INFO [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
- after this, nothing happens. The deployment never finishes. Other apps are deployed successfully as shown in preceding lines of the logs:
INFO [localhost-startStop-1] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory /usr/local/tomcat/webapps/examples has finished in 525 ms
when I log in to the interactive shell of the jasperserver container is around 2000-3000. So I assume the entropy is not the issue. The only other issue I can see in the logs is in the `localhost.2018-04-17.log` file which has the line
INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log No Spring WebApplicationInitializer types detected on classpath
in it and ends with the line:
INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log Initializing Spring root WebApplicationContext
I'm guessing that Catalina is stuck at this step. I've also attempted to analyze the thread dump of the application, but having limited experience in Java, couldn't locate the problem.
Any help is much appreciated.