I bet some uncaught exception kills the job... Just a guess
On Jul 30, 2012, at 12:48 PM, sommeralex <alexander.som...@gmail.com> wrote:
> hi!
>
> I have defined a schedule job within my service class, which seems to STOP
> after some calls.
>
> @Scheduled(fixedDelay=1800000) // 30min 1800000
> public void deleteOutdatedWeatherEntries() {
> System.out.println("clean cache:" + new Date());
> logger.info("CLEAN-UP TASK: Delete outdated entries.");
> myDAO.deleteEntries();
> }
>
> The console prints every 30min the logger info & System.out.print - but,
> after some time, it stops. there is no output anymore and the DB is not
> deleted anymore.
>
> I know that this is a spring issue, but maybe someone has an answer.
> instead, i could try the same with @Startup public static void scheduleJobs.
>
> But anyway, i wonder why the service stops..
>
>
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/scheduled-services-stops-Scheduled-fixedDelay-1800000-tp5714882.html
> Sent from the Tapestry - User mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
