[jira] [Updated] (FINERACT-276) Job scheduler timezones not handled correctly
[ https://issues.apache.org/jira/browse/FINERACT-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-276: -- Fix Version/s: (was: 1.9.0) > 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 >Affects Versions: 1.8.0 >Reporter: Santosh Math >Priority: Critical > Labels: p1 > Fix For: 3.0.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.20.10#820010)
[jira] [Updated] (FINERACT-276) Job scheduler timezones not handled correctly
[ https://issues.apache.org/jira/browse/FINERACT-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-276: -- Fix Version/s: 3.0.0 > 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 >Affects Versions: 1.8.0 >Reporter: Santosh Math >Priority: Critical > Labels: p1 > Fix For: 1.9.0, 3.0.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.20.10#820010)
[jira] [Updated] (FINERACT-276) Job scheduler timezones not handled correctly
[ https://issues.apache.org/jira/browse/FINERACT-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandar Vidakovic updated FINERACT-276: -- Fix Version/s: 1.9.0 (was: 1.8.0) > 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 >Affects Versions: 1.8.0 >Reporter: Santosh Math >Priority: Critical > Labels: p1 > Fix For: 1.9.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.20.10#820010)
[jira] [Updated] (FINERACT-276) Job scheduler timezones not handled correctly
[ https://issues.apache.org/jira/browse/FINERACT-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Vorburger updated FINERACT-276: --- Priority: Critical (was: Major) > 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: Critical > 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)
[jira] [Updated] (FINERACT-276) Job scheduler timezones not handled correctly
[ https://issues.apache.org/jira/browse/FINERACT-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-276: -- Fix Version/s: (was: 1.4.0) 1.5.0 > 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 >Assignee: Shruthi M R >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 (v7.6.3#76005)
[jira] [Updated] (FINERACT-276) Job scheduler timezones not handled correctly
[ https://issues.apache.org/jira/browse/FINERACT-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-276: -- Fix Version/s: (was: 1.3.0) 1.4.0 > 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 >Assignee: Shruthi M R >Priority: Major > Labels: p1 > Fix For: 1.4.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 (v7.6.3#76005)
[jira] [Updated] (FINERACT-276) Job scheduler timezones not handled correctly
[ https://issues.apache.org/jira/browse/FINERACT-276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Santosh Math updated FINERACT-276: -- Fix Version/s: 1.3.0 > 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 >Assignee: Markus Geiss >Priority: Major > Labels: p1 > Fix For: 1.3.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 (v7.6.3#76005)
