Any suggestions on best ways to write a “health check” page to be called by load balancers?
My app is getting big, and the traffic is big. If the app fails (hopefully never, but it’s a JVM) and the traffic is heavy enough, startup never seems to complete - every request times out, the app log goes quiet, and CPU goes to 100%. It appears to be due to race conditions possibly involving asset compression, minimising, and first time into the pages. I’m considering having a startup service crawl every page, in every language, in every skinning, before setting a singleton flag that the health check page will read to determine whether the app is ready to receive traffic. Is there a simpler way? Geoff --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
