Service timezone issues #29

New issue

Closed

opened 2018-06-29 01:27:36 +00:00 by jamie · 1 comment

jamie commented

2018-06-29 01:27:36 +00:00

(Migrated from git.hazaar.io)

The fix for this is two-fold:

If the service has no timezone configured, do not set a timezone. Ie: no longer default to UTC and just leave it as is.
Upstream from that, pass the Server timezone in the service startup packet and set that in the application before starting the service.

This will mean that if the service has no timezone configured, it will use the server timezone and if the server has no timezone configured, it will use UTC.

I have a service that has scheduled actions that did not appear to be running. Turned out to be a timezone issue since adding timezone support to services. Looks like support was not complete in that if a service was not configured with a timezone, it would use UTC, which is what was happening in this case. The server was configured to use Sydney time so with the service running on UTC scheduled tasks were executing 10 hours late. The fix for this is two-fold: * If the service has no timezone configured, do not set a timezone. Ie: no longer default to UTC and just leave it as is. * Upstream from that, pass the Server timezone in the service startup packet and set that in the application before starting the service. This will mean that if the service has no timezone configured, it will use the server timezone and if the server has no timezone configured, it will use UTC.

jamie commented

2018-06-29 01:28:42 +00:00

(Migrated from git.hazaar.io)

closed via commit fa85bbebf5

closed via commit fa85bbebf54d950554b3a0a23320b825bc7aac2c