Tomcat Activation Priority Too High

[chrishager82]

We have encountered an issue, where the tomcat services are starting too early in the init.d boot order. It appears that the instances have an activation priority of 50, and we would like to define that attribute.

[nibroc]

We're also seeing this. Some of our Tomcat applications load data into caches at startup which can take up to 10 minutes. This is resulting in ssh being unresponsive for a long time after reboot since process starting is blocked on Tomcat and sshd starts after it.

[chrishager82]

I found a manual solution via https://serverfault.com/questions/754676/how-to-change-the-startup-order-of-linux-init-scripts-in-redhat-centos. Adding a chkconfig line to the init script w/desired start/stop priorities, then running chkconfig reset, updates the priority. Still evaluating this cookbook to see if there's a way to set this via attribute.