<p>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).</p>

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

CC BY-SA 3.0
2016-06-07T11:20:04.680Z
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
CC BY-SA 3.0
2016-06-07T11:12:43.053Z
2016-06-07T11:12:43.053Z
Jonas Schnelli
<p>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 <code>The operation has timed out</code> exception. What is wrong with it? This unstable behavior is really annoys me.</p>

<p>My <code>bitcoin.conf</code> is:</p>

<pre><code>rpcuser = XXXXXXXX
rpcpassword = XXXXXXXX
server=1
rpcallowip=xx.xx.xx.xx
rpcallowip=127.0.0.1
rpcport=xxxx
rpcthreads=1200
</code></pre>

<p><strong>UPDATE:</strong> I use heavily edited <a href="https://github.com/GeorgeKimionis/BitcoinLib" rel="nofollow">https://github.com/GeorgeKimionis/BitcoinLib</a>, which in its turn internally is based on <code>HttpWebRequest</code>. <code>RpcRequestTimeoutInSeconds</code> is set to 60 seconds. Is it not enough to get balance and account list?</p>

CC BY-SA 3.0
2016-06-07T10:53:20.750Z
What kind of RPC calls are you issuing?
Pieter Wuille
CC BY-SA 3.0
2016-06-07T11:16:58.180Z
@PieterWuille, I updated my question.
Denis
<bitcoin-core><json-rpc>
Random 'The operation has timed out' errors in JSON-RPC
Denis
# Random 'The operation has timed out' errors in JSON-RPC

(Asked by: username_0 on 2016-06-07)

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
server=1
rpcallowip=xx.xx.xx.xx
rpcallowip=127.0.0.1
rpcport=xxxx
rpcthreads=1200

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?

**Tags:** bitcoin-core, json-rpc

> **Comments:**
> **username_1**: What kind of RPC calls are you issuing?  
> **username_0**: @PieterWuille, I updated my question.  

---

## 1 answers

### Answer by username_2 on 2016-06-07. Score: 2

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.

> **Comments:**
> **username_0**: As I see timeout can occur literally in any RPC call. More often in 'ListAccounts', then in 'GetAccountAddress', sometimes even in 'Move' and 'SendRawTransaction'.  

---

