rippled: Websocket timeout issues

With 0.50.2 repeated calls to ledger_data whilst also streaming the ledger and transaction streams leads to timeouts in the Server code in rippled with log_level set to trace:

2017-Feb-22 20:10:35 Server:TRC Websocket received '
{
        "binary" : true,
        "command" : "ledger_data",
        "id" : 39,
        "ledger" : 27861637,
        "marker" : "1AC61580EF42AA58D69059995313F05C5342E6AC2BA6A46A51EFB508C0F79C75"
}
'
2017-Feb-22 20:10:35 Server:TRC Websocket received '
{
        "binary" : true,
        "command" : "ledger_data",
        "id" : 40,
        "ledger" : 27861637,
        "marker" : "1B7EA1321C09D8421502B0A63EAD615EA3CB92EEB6393909312EA76C002C7289"
}
'
2017-Feb-22 20:10:35 Server:TRC ##22 timer: Connection timed out
2017-Feb-22 20:10:35 Server:TRC ##23 read: End of file
2017-Feb-22 20:10:35 Server:TRC ##24 write: Broken pipe

Problem is not seen in 0.40.

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 72 (59 by maintainers)

Commits related to this issue

Cancel websocket timer on failure: This fixes a problem where the timeout timer would not be canceled with some errors. fix #2026 — committed to miguelportilla/rippled by miguelportilla 7 years ago
Cancel websocket timer on failure: This fixes a problem where the timeout timer would not be canceled with some errors. fix #2026 — committed to seelabs/rippled by miguelportilla 7 years ago
Cancel websocket timer on failure: This fixes a problem where the timeout timer would not be canceled with some errors. fix #2026 — committed to seelabs/rippled by miguelportilla 7 years ago

Most upvoted comments

Now it seems stable. My bots lost around 100k XRP…but fine…maybe I should stop this “business” 😃

tuloski on Apr 10, 2017

@miguelportilla

{
        "command" : "subscribe",
        "id" : 1,
        "streams" : [ "ledger", "transactions", "server" ]
}

donovanhide on Mar 31, 2017

@nbougalis Have tested Mickey’s pull request locally and have had a few days of no disconnects on the subscribe stream connection. I did experience a write timeout on my second connection which submits transactions, although haven’t been able to replicate that yet with trace logging enabled.

donovanhide on Mar 29, 2017

Yep, can’t paste in the git log, but that’s the exact commit I’m using. Gaps are longer between disconnections, but still occurs.

donovanhide on Mar 24, 2017