On 19/08/17 20:02, Nicholas Hagen wrote:
> Is this the expected behavior now with Tomcat? If so, are there better
> recommendations on how to have a general purpose health check wait until
> the web applications are fully init'd?
I do not see the behaviour you describe with the latest 8.5.x bu
We are updating our applications to Spring Boot using Tomcat Embedded.
Previously we were on the 7.x version running standalone Tomcat with WAR
deployments. In our application we have two main servlets: a general
purpose health check (used in all our services) and the specific web
application.
Since you told the context is rather huge, have you checked gc times? A
long running full gc can block the machine completely resulting in the
up/down behaviour from outside. GC options depend on JVM version I use:
export JAVA_OPTS="$JAVA_OPTS -XX:+DisableExplicitGC -verbose:GC
-XX:+PrintGCDetails
