Skip to content

Daylight saving time issue in CronExpression #26830

Closed
@poutsma

Description

@poutsma

Expressions set on the exact hour of a daylight saving time (such as "0 10 2 * * *" in timezone Central Europe) result in a null value being return for next, when passing a time before the turnover (for instance, 01:09:00).

This issue seems to be caused by the fix for #26744.

/cc @sbrannen

Metadata

Metadata

Assignees

Labels

in: coreIssues in core modules (aop, beans, core, context, expression)type: regressionA bug that is also a regression

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions