[
https://issues.apache.org/jira/browse/FINERACT-2525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18072904#comment-18072904
]
Siva Sai Udayagiri commented on FINERACT-2525:
----------------------------------------------
Opened PR #5763 for this issue.
Reproduced the MariaDB 12.2 snapshot-isolation failure and updated
SavingsAccountTransactionTest to accept the valid 403 conflict response:
"Record has changed since last read in table 'm_savings_account'".
Verified by rerunning the affected savings integration tests.
> Integration tests fail with MariaDB "Record has changed since last read" due
> to innodb_snapshot_isolation=ON
> ------------------------------------------------------------------------------------------------------------
>
> Key: FINERACT-2525
> URL: https://issues.apache.org/jira/browse/FINERACT-2525
> Project: Apache Fineract
> Issue Type: Task
> Reporter: Victor Romero
> Priority: Major
>
> Integration tests fail with MariaDB "Record has changed since last read" due
> to innodb_snapshot_isolation=ON
>
> In Apache Fineract the actual failures happen later inside the integration
> tests, after MariaDB and Fineract are already up. The common error is: Record
> has changed since last read I found this in the failing shards for:
> FeignTrialBalanceSummaryReportTest.testExternalAssetOwnerEntriesAppearInReport
> ExternalAssetOwnerTransferCancelTest
> InitiateExternalAssetOwnerTransferTest.saleTransferWithSameOwnerExternalIdInParallelShouldNotFail
> SavingsAccountTransactionTest.testDeadlockSavingsBatchTransactions
> SavingsAccountTransactionTest.testConcurrentSavingsBatchTransactions
> The affected tables are:
> m_external_asset_owner_transfer
> m_savings_account
>
> Related to [https://github.com/apache/fineract/pull/5566]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
