Our test environment is finding itself in a state once a day where jsreport seems to be hung.
Every request from this point fails with a 500 error. Including a simple jsreport studio (WebUI) Run for a simple text with no transformations.
Timeout error during executing script Error: Timeout error during executing script
at null._onTimeout (..........\node_modules\script-manager\lib\manager-processes.js:24:8)
Killing the largest memory node.exe process actually stops all the new instances as well and resolves the issue.
The number of times it takes to cause the server to fail seems dependent upon the size of the report being run, small ones take about 100 runs, whereas larger ones take around 35 times before constant failure (with a 500 error).
This seems to be a memory leak to me...
Currently running under development mode...
Initializing jsreport@1.5.1 in development mode using configuration file dev.config.json
Setting process based strategy for rendering. Please visit http://jsreport.net/learn/configuration for information how to get more performance.
When I switch from using dedicated-process for phantom to phantom-server and from dedicated-process task strategy to http-server the problem seems to go away...
By the way I am running this through NodeIIS
Is dedicated-process not recommended for IIS?