This is silly, but yesterday night it worked! My app runs a cron job everyday at 2am my time (8:00 GMT). Often the job fails because of a timeout. You know, those timeouts one gets because the virtual server won't start.
Then I tried this silly solution. I run 5 dummy jobs 5, 4, 3, 2 and 1 minutes before the real one. Very funny, but yesterday night the 5 dummy jobs failed. Nevertheless, the real cron job started and ran OK!!! Come on, Google! This timeout problem has taken way too long to be solved. We were planning on going live with out app next Quarter. Now we are evaluating alternatives to move to another platform. We have spent over 6 months working on GAE and it looks like a wasted effort. /cronjob/DummyJob GAE warm up before recording charges for overdue payments @ 08:00 GMT every day 07:55 (UTC) 2010-03-10 07:55:02 on time Failed /cronjob/DummyJob GAE warm up before recording charges for overdue payments @ 08:00 GMT every day 07:56 (UTC) 2010-03-10 07:56:02 2 secs late Failed /cronjob/DummyJob GAE warm up before recording charges for overdue payments @ 08:00 GMT every day 07:57 (UTC) 2010-03-10 07:57:01 on time Failed /cronjob/DummyJob GAE warm up before recording charges for overdue payments @ 08:00 GMT every day 07:58 (UTC) 2010-03-10 07:58:01 on time Failed /cronjob/DummyJob GAE warm up before recording charges for overdue payments @ 08:00 GMT every day 07:59 (UTC) 2010-03-10 07:59:01 on time Failed /cronjob/PaymentsOverdueCharge Record charges for overdue payments @ 08:00 GMT every day 08:00 (UTC) 2010-03-10 08:00:01 on time Success Jorge Gonzalez -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
