You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Mihaly Dallos (Jira)" <ji...@apache.org> on 2023/07/28 13:46:00 UTC
[jira] [Assigned] (FINERACT-1941) Dangling executors in batch jobs
[ https://issues.apache.org/jira/browse/FINERACT-1941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mihaly Dallos reassigned FINERACT-1941:
---------------------------------------
Assignee: Norbert Táskai
> Dangling executors in batch jobs
> --------------------------------
>
> Key: FINERACT-1941
> URL: https://issues.apache.org/jira/browse/FINERACT-1941
> Project: Apache Fineract
> Issue Type: Bug
> Reporter: Norbert Táskai
> Assignee: Norbert Táskai
> Priority: Major
> Labels: PepperSoup
>
> The following batch jobs have dangling task executors created without properly managing their lifecycle:
> * SendMessageToSmsGatewayTasklet
> * SmsMessageScheduledJobServiceImpl
> * RecalculateInterestForLoanTasklet
> * PostInterestForSavingTasklet
> The *goal* of the story is to get rid of the Executors.newXYExecutor calls and replace them with properly initialized/destroyed Spring based task executors.
> {panel}
> {panel}
> {panel}
> *Acceptance criteria*
> * Spring’s TaskExecutors are used in the above listed batch jobs
> * The TaskExecutors are configurable via regular properties and environment variables
> {panel}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)