[
https://issues.apache.org/jira/browse/FINERACT-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Saghy updated FINERACT-1789:
---------------------------------
Labels: beginner-friendly (was: )
> retriveSchedulerDetail fails with Array index out of range: 0 on MySQL
> ----------------------------------------------------------------------
>
> Key: FINERACT-1789
> URL: https://issues.apache.org/jira/browse/FINERACT-1789
> Project: Apache Fineract
> Issue Type: Bug
> Components: Job Scheduler
> Affects Versions: 1.7.0
> Environment: Server OS: azul/zulu-openjdk-alpine:17 on docker
> container
> Database version: MySQL 8.0.26
> Database driver: org.mariadb.jdbc:mariadb-java-client:2.7.5
> Reporter: Carlos Fau
> Priority: Critical
> Labels: beginner-friendly
>
> h3. Description:
> When starting a new Fineract instance the
> *JobRegisterServiceImpl* loads all jobs calling
> *SchedularWritePlatformServiceJpaRepositoryImpl.retriveSchedulerDetail* which
> found no {*}SchedulerDetail{*}.
> Assuming that the JPA *findAll* will return a *null* response if no records
> found, it checks that and gets the first element of the returned array.
> {code:java}
> final List<SchedulerDetail> schedulerDetailList =
> this.schedulerDetailRepository.findAll();
> if (schedulerDetailList != null) {
> schedulerDetail = schedulerDetailList.get(0);
> }{code}
> The problem is that some JSP + Driver + Database instead of returning *null*
> when no records are found, it returns an empty array.
> h3. Steps to reproduce
> # Install mysql 8.0.26 (or use instance from GCE)
> # Deploy fineract on K8S
> # Fineract POD fails to start
> h3. Notes
> If confirmed I can provide a PR.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
