Some of your timers are schedules for a specific day of the month, so
they will fire again only in a month...
This is how the # separated string is created:
.append(second_).append(" # ")
.append(minute_).append(" # ")
.append( hour_).append(" # ")
.append( dayOfMonth_).append(" # ")
.append( month_).append(" # ")
.append( dayOfWeek_).append(" # ")
.append( year_).append(" # ")
.append( timezone_).append(" # ")
.append(((start_ == null) ? null : start_.getTime()))
.append(" # ")
.append(((end_ == null) ? null : end_.getTime()))
.append(" # ").append(automatic_);
if (automatic_) {
s.append(" # ").append(methodName_).append(" #
").append(paramCount_);
}
-marina
forums_at_java.net wrote:
> I have noticed that suddenly none of our Scheduled jobs are starting
> up at
> their specified intervals anymore.
>
> localhost:8080/ejb-timer-service-app/timer shows
> .... Welcome to Timer Application
>
> There are 30 active persistent timers on this container
>
> There are 0 active non-persistent timers on this container
>
> I tried adding a new ear file which uses the Schedule to say Hello Wolrd
> every minute, and it runs fine. Only our Application has somehow
> suddenly
> stopped working. Can someone give me an idea? I have logged into the
> Embedded Derby DB, and I see that there are entries for our applications,
> but they are not kicking off. I have attached the EJB__TIMER_TBL data
> for 2
> separate nodes, one that works and one that does not.
>
> Do you think if I go ahead and delete all the entries from
> EJB__TIMER_TBL,
> it might work?
>
>
>
>
> --
>
> [Message sent by forum member 'rdarbh']
>
> View Post: http://forums.java.net/node/884307
>
>
>