I’ve got tomcat 8.5.9 installed on a CentOS 7.2 droplet. When I restart tomcat, with only the tomcat manager in the webapps directory, restarts take anywhere from 3 to 15 minutes, and sometimes even longer. Has anyone seen such behavior? Top doesn’t show much CPU or memory being consumed by Java. We’re running OpenJDK 1.8.0_111. Normal restart times with no webapps is a couple of seconds on other systems.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Sign up for Infrastructure as a Newsletter.
Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Slow start up times for Tomcat are often related to Java’s
SecureRandom
implementation. By default, it uses/dev/random
as an entropy source. This can be slow as it uses system events to gather entropy (e.g. disk reads, key presses, etc). As theurandom
manpage states:One work around is to use
/dev/urandom
instead as it does not block. This is defined in yourJAVA_OPTS
That can be set in a number of places depending on how you set up Tomcat in the first place. It will usually be the init script or systemd service file used to start Tomcat.See this tutorial for more information.
Another option is to use haveged to generate more entropy. On CentOS, you can do so with:
For more information on how haveged works, check out this tutorial: