borikas commented on PR #3854: URL: https://github.com/apache/fineract/pull/3854#issuecomment-2147437664
> > > @adamsaghy I'm sorry for the delay. (I thought I could quickly deal with the problem and then write back, but no). I'm a bit stuck with these two tests right now: `ClientLoanIntegrationTest - testLoanCharges_INSTALLATION_FEE`. `SchedulerJobsTestResults - testInterestTransferForSavings`. > > > They started to fail for me after this commit [c267bfd](https://github.com/apache/fineract/commit/c267bfd61902c9313c2a1c4dc5f598104d5c3188), they do not pass without an annotation @transactional(propagation = Propagation.REQUIRES_NEW) The first one does not pass without this annotation on the `fetchPostInterestTransactionIds` method in the `AccountTransfersReadPlatformServiceImpl` class. And the second without it on the `retrieveLoanLinkedAssociation` method in the `AccountAssociationsCustomRepositoryImpl` class. > > > I will work further and try to solve this ASAP. > > > > > > @adamsaghy It looks like we have a problem with caching sql queries when migrating from jdbcTemplate to queryDSL, because queryDSL uses EntityManager Cache, at the same time as jdbcTemplate uses Spring Cache. > > I might not yet fully understand the issue. Are we talking about the prepared statement cache? Or the entity cache, rather when something was already fetched, it does not go to the database to fetch again? This problem is similar to an incorrect sequence of sql queries within the same transaction <img width="905" alt="Снимок экрана 2024-06-04 в 15 21 38" src="https://github.com/apache/fineract/assets/2794353/1e2de8ac-1916-4e90-a563-a55cf0731778";> <img width="905" alt="Снимок экрана 2024-06-04 в 15 21 58" src="https://github.com/apache/fineract/assets/2794353/c4a5d8eb-af18-46bc-add5-7946d96f129d";> <img width="994" alt="Снимок экрана 2024-06-04 в 15 24 22" src="https://github.com/apache/fineract/assets/2794353/2085c7b3-dd70-4d4e-9ea1-9854aab6433e";> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
