From 90f3d2568afa408353f9ce2290f15a92ba016fe3 Mon Sep 17 00:00:00 2001 From: CalDescent Date: Sun, 30 Jan 2022 19:00:28 +0000 Subject: [PATCH] Log whenever the synchronizer can't obtain a blockchain lock, so that blockchain lock issues are more easily noticed. --- src/main/java/org/qortal/controller/Synchronizer.java | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/main/java/org/qortal/controller/Synchronizer.java b/src/main/java/org/qortal/controller/Synchronizer.java index 1e3750cb..7eabcb9c 100644 --- a/src/main/java/org/qortal/controller/Synchronizer.java +++ b/src/main/java/org/qortal/controller/Synchronizer.java @@ -571,9 +571,11 @@ public class Synchronizer { // Make sure we're the only thread modifying the blockchain // If we're already synchronizing with another peer then this will also return fast ReentrantLock blockchainLock = Controller.getInstance().getBlockchainLock(); - if (!blockchainLock.tryLock()) + if (!blockchainLock.tryLock()) { // Wasn't peer's fault we couldn't sync + LOGGER.info("Synchronizer couldn't acquire blockchain lock"); return SynchronizationResult.NO_BLOCKCHAIN_LOCK; + } try { try (final Repository repository = RepositoryManager.getRepository()) {