Skip to content

CronSequenceGenerator fails to accurately compute earliest next date when using second expression [SPR-9459] #14094

Closed
@spring-projects-issues

Description

@spring-projects-issues

sebdotv opened SPR-9459 and commented

If using an expression containing seconds like "*/15 * 1-4 * * *", CronSequenceGenerator will compute the following next dates:

  • from 01-june-2012 9:53:50 -> the next day at 1:00:00, which is correct
  • from 01-june-2012 9:53:00 -> the next day at 1:00:15, which is not the earliest possible schedule (above)

Corresponding test case attached.


Affects: 3.1.1

Attachments:

Issue Links:

Metadata

Metadata

Assignees

Labels

in: coreIssues in core modules (aop, beans, core, context, expression)type: bugA general bug

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions