Abhishek6122008 commented on code in PR #6591: URL: https://github.com/apache/fineract/pull/6591#discussion_r4273999484
########## fineract-savings/src/test/java/org/apache/fineract/portfolio/savings/domain/SavingsAccountRepositoryWrapperLockOrderTest.java: ########## @@ -0,0 +1,62 @@ +/** + * Licensed to the Apache Software Foundation (ASF) under one + * or more contributor license agreements. See the NOTICE file + * distributed with this work for additional information + * regarding copyright ownership. The ASF licenses this file + * to you under the Apache License, Version 2.0 (the + * "License"); you may not use this file except in compliance + * with the License. You may obtain a copy of the License at + * + * http://www.apache.org/licenses/LICENSE-2.0 + * + * Unless required by applicable law or agreed to in writing, + * software distributed under the License is distributed on an + * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + * KIND, either express or implied. See the License for the + * specific language governing permissions and limitations + * under the License. + */ +package org.apache.fineract.portfolio.savings.domain; + +import static org.mockito.Mockito.mock; +import static org.mockito.Mockito.never; +import static org.mockito.Mockito.verify; + +import java.util.List; +import org.junit.jupiter.api.Test; +import org.mockito.ArgumentMatchers; + +/** + * Two transfers in opposite directions (A to B and B to A) deadlock when each locks its own account first. The accounts + * are therefore always locked in ascending id order, whatever the direction of the transfer. + */ +class SavingsAccountRepositoryWrapperLockOrderTest { Review Comment: These mock tests can't prove the deadlock is fixed. Could you add an integration test that runs A→B and B→A transfers concurrently and asserts all succeed? -- 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]
