<p>Something is trying to make too many simultaneous RPC requests.</p>
<p>Running parallel jobs making RPC requests, I've noticed that only 2 requests can be made simultaneously for certain things, and even then it occasionally threw <code>error: Server response: Work queue depth exceeded</code>.</p>

CC BY-SA 4.0
2024-04-26T21:27:05.937Z
2024-04-26T21:27:05.937Z
Geremia
<p>I am trying to make rpc calls to an Rpc Interface &quot;listunspent&quot;. So i get this Error: ESOCKETTIMEDOUT. I checked the bitcoin node debug file and saw the error message &quot;Depth queue work exceeded&quot;. I have added this option rpcworkqueue= settings to the bitcoin.conf file.</p>
<p>Here is my bitcoin.conf file</p>
<pre><code>prune=550 port=8333 rpcworkqueue=1000 rpcuser=user rpcpassword=userpass zmqpubrawblock=tcp://127.0.0.1:29000 zmqpubrawtx=tcp://127.0.0.1:29000 zmqpubhashtx=tcp://127.0.0.1:29000 zmqpubhashblock=tcp://127.0.0.1:29000
</code></pre>
<p>The following is the error response i get while trying to make rpc calls from my node app</p>
<pre><code>{
&quot;status&quot;: 500,
&quot;error&quot;: {
    &quot;name&quot;: &quot;RequestError&quot;,
    &quot;message&quot;: &quot;Error: ESOCKETTIMEDOUT&quot;,
    &quot;cause&quot;: {
        &quot;code&quot;: &quot;ESOCKETTIMEDOUT&quot;,
        &quot;connect&quot;: false
    },
    &quot;error&quot;: {
        &quot;code&quot;: &quot;ESOCKETTIMEDOUT&quot;,
        &quot;connect&quot;: false
    },
    &quot;options&quot;: {
        &quot;auth&quot;: {
            &quot;user&quot;: &quot;user&quot;,
            &quot;pass&quot;: &quot;userpass&quot;
        },
        &quot;uri&quot;: &quot;/&quot;,
        &quot;baseUrl&quot;: &quot;http://127.0.0.1:8332&quot;,
        &quot;timeout&quot;: 30,
        &quot;json&quot;: true,
        &quot;body&quot;: {
            &quot;method&quot;: &quot;listunspent&quot;,
            &quot;params&quot;: {},
            &quot;jsonrpc&quot;: 1,
            &quot;id&quot;: &quot;rpc-bitcoin&quot;
        },
        &quot;method&quot;: &quot;POST&quot;,
        &quot;simple&quot;: true,
        &quot;resolveWithFullResponse&quot;: false,
        &quot;transform2xxOnly&quot;: false
    }
}
</code></pre>
<p>}</p>
<p>Any help to solve this?</p>

<bitcoind><json-rpc>
Rpc work Queue Exceeded
Abbeville
# Rpc work Queue Exceeded

(Asked by: username_0 on 2023-02-03)

I am trying to make rpc calls to an Rpc Interface "listunspent". So i get this Error: ESOCKETTIMEDOUT. I checked the bitcoin node debug file and saw the error message "Depth queue work exceeded". I have added this option rpcworkqueue= settings to the bitcoin.conf file.

Here is my bitcoin.conf file

```
prune=550 port=8333 rpcworkqueue=1000 rpcuser=user rpcpassword=userpass zmqpubrawblock=tcp://127.0.0.1:29000 zmqpubrawtx=tcp://127.0.0.1:29000 zmqpubhashtx=tcp://127.0.0.1:29000 zmqpubhashblock=tcp://127.0.0.1:29000

```

The following is the error response i get while trying to make rpc calls from my node app

```
{
"status": 500,
"error": {
    "name": "RequestError",
    "message": "Error: ESOCKETTIMEDOUT",
    "cause": {
        "code": "ESOCKETTIMEDOUT",
        "connect": false
    },
    "error": {
        "code": "ESOCKETTIMEDOUT",
        "connect": false
    },
    "options": {
        "auth": {
            "user": "user",
            "pass": "userpass"
        },
        "uri": "/",
        "baseUrl": "http://127.0.0.1:8332",
        "timeout": 30,
        "json": true,
        "body": {
            "method": "listunspent",
            "params": {},
            "jsonrpc": 1,
            "id": "rpc-bitcoin"
        },
        "method": "POST",
        "simple": true,
        "resolveWithFullResponse": false,
        "transform2xxOnly": false
    }
}

```

}

Any help to solve this?

**Tags:** bitcoind, json-rpc


---

## 1 answers

### Answer by username_1 on 2024-04-26. Score: 0

Something is trying to make too many simultaneous RPC requests.

Running parallel jobs making RPC requests, I've noticed that only 2 requests can be made simultaneously for certain things, and even then it occasionally threw `error: Server response: Work queue depth exceeded`.


---

