Bug: Getting ECONNRESET error when running simple test with http loop
See original GitHub issueEver since the pull request https://github.com/artilleryio/artillery/pull/557 merged into master, simple tests with configs that have http.pool configured are failing with error: Error: socket hang up: ECONNRESET
Test file:
{
"config": {
"target": "https://httpstat.us",
"http": {
"pool": 3
},
"phases": [{
"duration": 1,
"arrivalRate": 3
}]
},
"scenarios": [{
"name": "Get response code 200",
"flow": [{
"get": {
"url": "/200",
"forever": true
}
}]
}]
}
Results:
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
read econnreset at tcp.onstreamread (node:internal ... - You.com
I always get this error : in node when I use promises in socket.io to get image files from database. Where actually is...
Read more >supertest failing with ECONNRESET - Stack Overflow
I'm working on a Node.js project and trying to write test cases for the app. The endpoints are working perfectly fine when I...
Read more >RTOS/66AK2H12: Client Socket recv() returns -1 and ... - TI E2E
When I send a 'large' stream from the EVM server to the EVM client, the client recv() returns -1 and fdError() gives 54,...
Read more >Possible bug with multiple fetch? - phyphox Forums
I am doing multiple 'basic' get with 'http://192.168.0.5:8080/get?acc_time=0.41327542&accX= ... the second and so on error with ECONNRESET.
Read more >Bug listing with status RESOLVED with resolution FIXED as at ...
Bug :2 - "How do I attach an ebuild. ... Bug:192 - "lftp ebuild does not compile the ftp,http,ect modules needed for it...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
My pleasure. Something to consider when you are looking at a fix for this bug is the version of request.js npm package. When running artillery tests using request.js version 2.87, I could reach 1500 RPS testing a simple server that returned only 200 locally on my machine. However, when I used the most up to date version of request.js, 2.88, I could reach only ~750 RPS. I ran these tests with a pool of 100 sockets where I let request.js handle the logic of the sockets (basically by reverting the commit that introduced this bug https://github.com/artilleryio/artillery/issues/621)
It’s important to take into account this significant difference in performance between the two request.js versions
thanks for the bug report @NivLipetz; re performance differences between
request.js
versions – that’s very interesting and something to look into, I’ll create a separate ticket for it