Qortal/qortal
1
0
Fork 0
mirror of https://github.com/Qortal/qortal.git synced 2025-07-19 19:01:22 +00:00
Code Issues Packages Projects Releases Wiki Activity

added cooling period in case of re-connections

Browse Source
This commit is contained in:
PhilReact 2025-07-10 14:40:13 +03:00
parent 256baeb1f4
commit e5890b3b6f
1 changed files with 16 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
src/main/java/org/qortal/network/PeerSendManager.java
View File

@ -13,6 +13,7 @@ import org.qortal.network.message.Message;
public class PeerSendManager {
private static final Logger LOGGER = LogManager.getLogger(PeerSendManager.class);
private volatile boolean coolingDown = false;
private static final int MAX_RETRIES = 15;
private static final int BASE_RETRY_DELAY_MS = 100;
@ -75,8 +76,18 @@ private final ExecutorService executor = Executors.newSingleThreadExecutor(new T
peer,
MAX_RETRIES);
peer.disconnect("SendMessage retries exceeded");
coolingDown = true;
queue.clear();
break;
try {
Thread.sleep(30_000); // Give time for peer to possibly reconnect
} catch (InterruptedException e) {
Thread.currentThread().interrupt();
return;
}
coolingDown = false;
continue; // Loop again in case the peer reconnects
}
// Throttle after successful send
@ -95,6 +106,10 @@ private final ExecutorService executor = Executors.newSingleThreadExecutor(new T
private volatile long lastUsed = System.currentTimeMillis();
public void queueMessage(Message message) {
if (coolingDown) {
LOGGER.debug("PeerSendManager in cooldown, ignoring message {}", message.getId());
return; // or block/wait if you prefer
}
lastUsed = System.currentTimeMillis();
this.queue.offer(message);
}