Michael Vorburger created FINERACT-856:
------------------------------------------
Summary: Deadlock found when trying to get lock try restarting
transaction
Key: FINERACT-856
URL: https://issues.apache.org/jira/browse/FINERACT-856
Project: Apache Fineract
Issue Type: Bug
Reporter: Michael Vorburger
The integration test logs sometimes show:
{{Deadlock found when trying to get lock try restarting transaction}}
I'm not clear whether those are log messages that can be ignored, because there
is retry logic in place (e.g. in/by OpenJPA?), or if this indicates real
failures which we must handle with a retry logic in the code... some background:
* https://dev.mysql.com/doc/refman/8.0/en/innodb-deadlocks.html
* https://dev.mysql.com/doc/refman/8.0/en/innodb-deadlock-example.html
*
https://stackoverflow.com/questions/2332768/how-to-avoid-mysql-deadlock-found-when-trying-to-get-lock-try-restarting-trans
*
https://stackoverflow.com/questions/17747906/getting-deadlock-found-when-trying-to-get-lock-try-restarting-transaction/17748793
* https://dzone.com/articles/automatic-deadlock-retry
* https://github.com/SOCI/soci/issues/518
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
