recognizing too high nonce

Question

We have a cluster of servers which run a service. This services are broadcasting transactions from one address to many different addresses. The problem now is, that they work in parallel. This means, that they always need to know the next valid nonce. Sometimes it happens that a service tries to broadcast a transaction with a nonce which is too high. For example lets say the last transaction of address "0xabc..." has the nonce 100. Now one service tries to broadcast a raw transaction with a nonce of 102 instead of the valid 101like this:

web3j.ethSendRawTransaction(rawMessageWithNonce102).send();

Is there any way of detecting the issue?

web3j of course does not through an error here, because initially the tx gets into the tx pool. But after some time its deleted from there.

How can I detect a "too high nonce issue" in my java application? Any ideas?

Answer 1

Not sure how you can detect it, but you could maybe cache the current nonce, ie. in Redis, and then check that value whenever you are sending the transaction. Once the transaction is sent, update the nonce and each server would share the same instance of cache.