0

I am using QueuingTransactionReceiptProcessor() with callback accept(). DEFAULT_POLLING_ATTEMPTS_PER_TX_HASH is 10 and POLLING_FREQUENCY is 15000. That gives nearly 3 min wait for network to acknowledge. But I noticed that ethereum mainnet takes 8 to 10 minutes to give a response. At the end of timeout window (which leads to exception), i want to check if TxHash is still in pending state with the network and if so extend the timeout interval. Timeout does not really mean transaction has failed on the network. It could mean I need to wait for more time. it works fine on r

  • no issues on rinkeby as the transactions complete under 150 seconds – hd312 Feb 14 at 5:20
  • correction: I am using FastRawTransactionManager(). I don't think it makes a difference for the answer though – hd312 Feb 14 at 5:39
0

I havn't used "QueuingTransactionReceiptProcessor()" yet, but maybe this could help you

EthGetTransactionReceipt transactionReceipt =
                    web3j.ethGetTransactionReceipt(txHash).send();
if (transactionReceipt.getResult() != null && !transactionReceipt.hasError()) {             
    String statusOfTx =  transactionReceipt.getTransactionReceipt().get().getStatus();
    ..check the status and do something..
}

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.