I'm running a web-app using Jetty on Heroku Cedar stack and I noticed that the app does not react to SIGTERM and does not do a graceful shutdown. Every time I stop the process, restart it, deploy new version - whenever Heroku needs to stop running app I get something like this:
2012-05-15T20:41:43+00:00 heroku[web.2]: Stopping process with SIGTERM 2012-05-15T20:41:54+00:00 heroku[web.2]: Error R12 (Exit timeout) -> Process failed to exit within 10 seconds of SIGTERM 2012-05-15T20:41:54+00:00 heroku[web.2]: Stopping process with SIGKILL 2012-05-15T20:41:55+00:00 heroku[web.2]: Process exited with status 137 2012-05-15T20:41:55+00:00 heroku[web.2]: State changed from up to down My Procfile looks like this: web: java $JAVA_OPTS -Djetty.port=$PORT -jar target/dependency/jetty-runner.jar --lib target/dependency --config etc/jetty.xml etc/context.xml And when I run it locally and send SIGTERM to it it shuts down gracefully no problem. Does anyone have any clue on what's going on? Thanks, Lev. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/heroku?hl=en_US?hl=en
