Hi Charles,
I gave it a quick look and debugged
org.apache.tapestry5.ioc.internal.services.cron.CronExpression.getTimeAfter(Date)
with your expression and can confirm that there's an issue with handling
"L-".
At first, it got the right day, but then it gets reset to today.
The code is quite com
Hi,
There seems to be an issue with CronExpression using "L" (last day of
month).
When I place the following code in my AppModule, the job is triggered at
the appointed time, and then keeps executing over and over immediately
in a seemingly infinite loop. I can work around by using a
day-of
