I run Bitcoin Core QT and ASP.NET website on the same webserver. My website communicates with Bitcoin Core QT via JSON-RPC. There are hundreds of requests behind the scenes. Sometimes a request finishes with The operation has timed out exception. What is wrong with it? This unstable behavior is really annoys me.

My bitcoin.conf is:

rpcuser = XXXXXXXX
rpcpassword = XXXXXXXX

UPDATE: I use heavily edited https://github.com/GeorgeKimionis/BitcoinLib, which in its turn internally is based on HttpWebRequest. RpcRequestTimeoutInSeconds is set to 60 seconds. Is it not enough to get balance and account list?

  • What kind of RPC calls are you issuing? Jun 7 '16 at 10:53
  • @PieterWuille, I updated my question.
    – Denis
    Jun 7 '16 at 11:16

Some operation might take longer then your RPC clients timeout is set to. This could be either due to system workload or due to loading bigger sets of data over RPC (example: a wallet with 100'000 wallet transactions).

Try to debug which commands take long/longer and consider checking your RPC clients http timeout.

  • As I see timeout can occur literally in any RPC call. More often in 'ListAccounts', then in 'GetAccountAddress', sometimes even in 'Move' and 'SendRawTransaction'.
    – Denis
    Jun 7 '16 at 11:20

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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