Robert Baminger

@ba1dr, maybe this will help you: [https://github.com/highcharts/node-export-server/pull/488#issuecomment-2166427987](https://github.com/highcharts/node-export-server/pull/488#issuecomment-2166427987)

FYI, I also made this [https://github.com/highcharts/node-export-server/commit/d029d00144af238c7f28cb50f5a52d7079273ae1](https://github.com/highcharts/node-export-server/commit/d029d00144af238c7f28cb50f5a52d7079273ae1) addition, because of this error ... ``` Mon Jun 17 2024 09:17:00 GMT+0000 [warning] - [chart] Unable to load the default resources.json file. Error:...

@paukert, if you need a quick fix for this problem (so that the server runs), I've made a few changes here: https://github.com/highcharts/node-export-server/commit/d029d00144af238c7f28cb50f5a52d7079273ae1

**Any news on that @jszuminski ?** I've got the same Problem/Error ... ``` [error] - [pool] In pool.postWork: For request with ID 592be5b34baa44e3b875ec37ee157c6b - Error encountered when acquiring an available...

@jszuminski, I just found the commit that introduced this Problem :) These changes here https://github.com/highcharts/node-export-server/commit/b9bd1ed83d857baa77e777e6f8b3d26bac9bd4c1 in the `pool.js` are responsible for the error! See also the history here https://github.com/highcharts/node-export-server/commits/master/lib/pool.js It...

@jszuminski, sorry, but I celebrated a little bit too early :( After deploying the above Dockerfile/Image to Kubernetes, I made a stress test with **20 concurrent users** over **3 minutes**...

Further tests with Postman It works with **20 concurrent** users over **3 minutes** with `POOL_MIN_WORKERS=1` & `POOL_MAX_WORKERS=1` ... It DOESNT work with **100 concurrent** users over **3 minutes** with `POOL_MIN_WORKERS=1`...

I definitely seems that the **problem** arises with **more concurrent** users and it get's **worse** with **more workers**!

@jszuminski, @cvasseng or @PaulDalek, since you seem to be the main contributors for this project, could you please provide some Feedback to this issue and 2 (maybe) related issues ......

**@stitot, could you developers find a solution to this issue?** I've tested this issue again using v5.0.0 and different amounts of workers ... unfortunately the same error still occurs ......