[
https://issues.apache.org/jira/browse/FINERACT-1682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Saghy updated FINERACT-1682:
---------------------------------
Description:
When a job is inactive (does not scheduled), it still can be executed.
Unfortunately for inactive jobs the job key does not refreshed during
scheduling (which is fine), but without the job key refresh, these jobs will be
still executed, however the execution details transaction will fail if
multiple tenants are present.
When a job is executed 2 transaction is occurs:
1. The job's logic
2. Saving the jobs execution details
was:When a job is inactive (does not scheduled), it still can be executed.
Unfortunately for inactive jobs the job key does not refreshed during
scheduling (which is fine), but without the job key refresh, these jobs will
fail if multiple tenants are present
> Inactive job's job key does not refresh for multiple tenants
> ------------------------------------------------------------
>
> Key: FINERACT-1682
> URL: https://issues.apache.org/jira/browse/FINERACT-1682
> Project: Apache Fineract
> Issue Type: Bug
> Affects Versions: 1.8.0
> Reporter: Adam Saghy
> Assignee: Adam Saghy
> Priority: Major
> Fix For: 1.9.0
>
>
> When a job is inactive (does not scheduled), it still can be executed.
> Unfortunately for inactive jobs the job key does not refreshed during
> scheduling (which is fine), but without the job key refresh, these jobs will
> be still executed, however the execution details transaction will fail if
> multiple tenants are present.
> When a job is executed 2 transaction is occurs:
> 1. The job's logic
> 2. Saving the jobs execution details
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
