How to prevent tomcat terminating itself if startup time is >300s

Asked Nov 05 '13 at 14:36

Active Nov 05 '13 at 14:36

Viewed 163 times

I have a grails application running on tomcat that takes a ridiculously long time to start up. It runs in a VM, and the machine is shared by several other VMs. The application runs fast enough when it eventually starts, however it sometimes takes longer than 300 seconds to start up if there are lots of database migrations to run, for example.

If tomcat kills itself after 300 seconds, in the middle of a database migration, then obviously this isn't great.

Is it possible to extend the max startup time to >300 seconds?

asked Nov 05 '13 at 14:36

rcgeorge23

3,594
4
29
54

Possible duplicate [here](http://stackoverflow.com/questions/4845219/tomcat-timeout-eclipse). – dmahapatro Nov 05 '13 at 14:54
I'm running tomcat standalone, not in eclipse. Using grails run-war. Cheers. – rcgeorge23 Nov 05 '13 at 15:04
1

Possibly `grails.tomcat.startupTimeoutSecs = 500` in your build config? – Alidad Nov 05 '13 at 16:30
Looks like that did the trick, thanks. Go ahead and create an answer here & I'll accept if you're bothered about the reputation points ;-) – rcgeorge23 Nov 13 '13 at 13:05

How to prevent tomcat terminating itself if startup time is >300s

0 Answers0