Can it be that you renamed the server or the domain or changed by any
chance the appid in the domain.xml?
Can you try on 3.1.2 (or 3.1.1) to check if it's not a bug that was
somehow fixed?
thanks,
-marina
forums_at_java.net wrote:
> Thanks for the replies.
>
> We do have some Scheduled jobs that run only once a month, or some
> twice a
> month, but most of them are nightly. The one that is important for us
> runs
> every day at 06:00pm, and it is not running anymore along with our other
> nightly jobs.
>
> |0 # 0 # 18 # * # * # * # * # null # null # null # true #
> runScheduledWeeklyPaymentProcess # 0 @Schedule(minute = "0", hour = "18",
> dayOfWeek = "*"
> I have undeployed the application, and created a new deploy, and also
> re-started the machine to no avail. This was working for the last 6
> months,
> and it suddenly stopped working. Also during deploy we see that the
> timers
> are all restored, and there are no errors.
>
> As the other user suggested, maybe using persistent=false might help?
> Another
> option I want to try is to do a delete on the ejb__timer_tbl? I am not
> sure
> if that is safe or not?
>
> ij> delete from EJB__TIMER__TBL;
>
>
>
> --
>
> [Message sent by forum member 'rdarbh']
>
> View Post: http://forums.java.net/node/884307
>
>