I am launching a core application created by Jhipster - see the bottom of the setup information to be run on the same Heroku core speaker. I use the tomcat built-in approach and everything works fine except for the start time in the production profile.
Running the server locally on my machine using Foreman I get the following results:
- In the dev profile, I get a startup time of <30 seconds for the local and remote Heroku database.
- In the prod profile, this increases to> 100 seconds for both cases.
This causes Heroku to terminate the instance before launch is complete because they need to bind the server to the designated port within 60 seconds.
So my question is how / if I could reduce this time. I know that Heroku offers to increase the timeout interval to 120 seconds based on each application. I would appreciate a more elegant approach, however, especially because I work on a basic dino, so extending the timeout might not even be enough.
I also know Jetty / WebappRunner, but I prefer to stick with tomcat's simpler built-in settings, if at all possible.
Finally, I saw that for Rails, it is possible to use a proxy server at startup to bind directly to the Heroku port - I did not find the Spring equivalent.
Thanks in advance!
Customization
- jhipster v017.2
- authenticationType ":" token "
- hibernateCache ":" no "
- clusteredHttpSession ":" no "
- websocket ":" no "
- databaseType ":" sql "
- devDatabaseType ":" postgresql "
- prodDatabaseType ":" postgresql "
- useCompass ": true
- buildTool ":" maven ",
- frontendBuilder ":" grunt "
- javaVersion ":" 7 "