[jira] [Assigned] (FINERACT-276) Job scheduler timezones not handled correctly

["Michael Vorburger (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FINERACT-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Vorburger reassigned FINERACT-276:
------------------------------------------

    Assignee:     (was: Shruthi  M R)

Dear current assignee of this issue, related to FINERACT-1000 and to clean up our shiny brand new JIRA Dashboard on https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12335824 I'm doing a little bit of "release management" today, and because you have no updated in a very long time, have taken the liberty to assume that you have lost interest to contribute to this issue (the Fineract project is sad to have lost you!), and am therefore un-assigning it from you (in a "bulk" update, this message is not personal but is being commented in tens of issues today).

Un-assigning it from you makes it clear to other contributors that this issue would be available for them to work on, in the (rather unlikely, yes) case that they could be so inclined. Should this be a misunderstanding on my part, I apologize, ask you to clarify your intentions for this issue by replying by commenting back here - and do re-assigning it back to you!

> Job scheduler timezones not handled correctly
> ---------------------------------------------
>
>                 Key: FINERACT-276
>                 URL: https://issues.apache.org/jira/browse/FINERACT-276
>             Project: Apache Fineract
>          Issue Type: Bug
>          Components: Loan
>            Reporter: Santosh Math
>            Priority: Major
>              Labels: p1
>             Fix For: 1.5.0
>
>
> Reported by Sander  at  https://mifosforge.jira.com/browse/MIFOSX-1269
> Original Description:
> When investigating some issues with the overdue loan portfolio we found out that the current way the jobs are handled can cause differences in the figures for tenants by not picking up the correct date.
> The server has the timezone set to UTC/GMT. When a cronjob is added with a cron entry to run at 0:01 every day, the java scheduler converts this into the timezone of the tenant (UTC+3 in this example). In this case this results in the actual schedule to be kicked off at 21:01 the day before.
> When the job then triggers it on 21:01 on 01-06-2014 it uses the mysql CURDATE() feature to decide on the current date, but this returns in UTC, therefore reporting everything against 01-06-2014, instead of 02-06-2014 which was the expected (based on timezone UTC+3).
> In this case the arrears are updated incorrectly, but same applies to prepayments and all other jobs that happen in the gap between UTC and the tenant timezone.
> Workaround: Update the cronjob entry to run at 03:01 (UTC+3) by default, this then gets converted into 0:01 (UTC) and therefore it uses 02-06-2014 as the date.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)