Scheduled tasks and Umbraco.Web.Scheduling.KeepAlive error
We've experienced an issue which brought one of our sites down for a period and any help figuring out why would be appreciated.
Our application has a scheduled task running which calls a method AddSubscribersToEventAttendanceThanks on an UmbracoApiController called EventDataScheduledApiController. This method started throwing an exception due to a property on a content node being unexpectedly empty - obviously we should have been handling the null property - but this in itself wasn't causing a problem - the scheduled task call returns 'False' because the HttpStatus isn't OK and on it goes:
Until, at 13:32 the site shuts down - as happens periodically. When it comes back up at 13:40, Umbraco.Web.Scheduling.KeepAlive is failing, and the site is unavailable.
This continued until the next application shutdown, which occured at about 18:00 the next day, when the issue corrected itself, the site came back up, and the log entries return to the pattern shown in the first excerpt.
Does someone out there understand what happened here?
Scheduled tasks and Umbraco.Web.Scheduling.KeepAlive error
We've experienced an issue which brought one of our sites down for a period and any help figuring out why would be appreciated.
Our application has a scheduled task running which calls a method AddSubscribersToEventAttendanceThanks on an UmbracoApiController called EventDataScheduledApiController. This method started throwing an exception due to a property on a content node being unexpectedly empty - obviously we should have been handling the null property - but this in itself wasn't causing a problem - the scheduled task call returns 'False' because the HttpStatus isn't OK and on it goes:
Until, at 13:32 the site shuts down - as happens periodically. When it comes back up at 13:40, Umbraco.Web.Scheduling.KeepAlive is failing, and the site is unavailable.
This continued until the next application shutdown, which occured at about 18:00 the next day, when the issue corrected itself, the site came back up, and the log entries return to the pattern shown in the first excerpt.
Does someone out there understand what happened here?
is working on a reply...