Error when processing render request Error during rendering report

324 views
Skip to first unread message

br...@avalanchetech.com

unread,
Aug 8, 2015, 7:17:01 PM8/8/15
to jsreport
I am trying to render a very large report.  I'm not sure if JSReport is timing out or the data is too large.

I have "express.inputRequestLimit" : "1024mb" in my config file, this should be plenty large.  In JSReport error file, the error is listed below.

I am connecting to my onprem jsreport instance using the C# module available on GITHUB with no modifications.

Any guidance would be appreciated.

----------------------------------------------------------------------------------------------------------------------------------------------

2015-08-08T23:09:24.550Z - error: Error when processing render request Error during rendering report: read ECONNRESET Error: read ECONNRESET
    at errnoException (net.js:904:11)
    at TCP.onread (net.js:558:19)
From previous event:
    at Reporter.render (C:\JSREPORT\node_modules\jsreport\lib\reporter.js:185:53)
    at C:\JSREPORT\node_modules\jsreport\extension\express\lib\routes.js:141:18
    at Layer.handle [as handle_request] (C:\JSREPORT\node_modules\jsreport\node_modules\express\lib\router\layer.js:82:5)
    at next (C:\JSREPORT\node_modules\jsreport\node_modules\express\lib\router\route.js:110:13)
    at Route.dispatch (C:\JSREPORT\node_modules\jsreport\node_modules\express\lib\router\route.js:91:3)
    at Layer.handle [as handle_request] (C:\JSREPORT\node_modules\jsreport\node_modules\express\lib\router\layer.js:82:5)
    at C:\JSREPORT\node_modules\jsreport\node_modules\express\lib\router\index.js:267:22
    at Function.proto.process_params (C:\JSREPORT\node_modules\jsreport\node_modules\express\lib\router\index.js:321:12)
    at next (C:\JSREPORT\node_modules\jsreport\node_modules\express\lib\router\index.js:261:10)
    at serveStatic (C:\JSREPORT\node_modules\jsreport\node_modules\serve-static\index.js:59:14)
    at Layer.handle [as handle_request] (C:\JSREPORT\node_modules\jsreport\node_modules\express\lib\router\layer.js:82:5)
    at trim_prefix (C:\JSREPORT\node_modules\jsreport\node_modules\express\lib\router\index.js:302:13)
    at C:\JSREPORT\node_modules\jsreport\node_modules\express\lib\router\index.js:270:7
    at Function.proto.process_params (C:\JSREPORT\node_modules\jsreport\node_modules\express\lib\router\index.js:321:12)
2015-08-08T23:09:24.550Z - error: Error during processing request: https://10.0.2.41/api/report details: Error during rendering report: read ECONNRESET Error: read ECONNRESET
    at errnoException (net.js:904:11)
    at TCP.onread (net.js:558:19)
From previous event:
    at Reporter.render (C:\JSREPORT\node_modules\jsreport\lib\reporter.js:185:53)
    at C:\JSREPORT\node_modules\jsreport\extension\express\lib\routes.js:141:18
    at Layer.handle [as handle_request] (C:\JSREPORT\node_modules\jsreport\node_modules\express\lib\router\layer.js:82:5)
    at next (C:\JSREPORT\node_modules\jsreport\node_modules\express\lib\router\route.js:110:13)
    at Route.dispatch (C:\JSREPORT\node_modules\jsreport\node_modules\express\lib\router\route.js:91:3)
    at Layer.handle [as handle_request] (C:\JSREPORT\node_modules\jsreport\node_modules\express\lib\router\layer.js:82:5)
    at C:\JSREPORT\node_modules\jsreport\node_modules\express\lib\router\index.js:267:22
    at Function.proto.process_params (C:\JSREPORT\node_modules\jsreport\node_modules\express\lib\router\index.js:321:12)
    at next (C:\JSREPORT\node_modules\jsreport\node_modules\express\lib\router\index.js:261:10)
    at serveStatic (C:\JSREPORT\node_modules\jsreport\node_modules\serve-static\index.js:59:14)
    at Layer.handle [as handle_request] (C:\JSREPORT\node_modules\jsreport\node_modules\express\lib\router\layer.js:82:5)
    at trim_prefix (C:\JSREPORT\node_modules\jsreport\node_modules\express\lib\router\index.js:302:13)
    at C:\JSREPORT\node_modules\jsreport\node_modules\express\lib\router\index.js:270:7
    at Function.proto.process_params (C:\JSREPORT\node_modules\jsreport\node_modules\express\lib\router\index.js:321:12)

Jan Blaha

unread,
Aug 9, 2015, 4:16:02 PM8/9/15
to jsreport
We were able to simulate this and trying to find a solution now.

The workaround is to change config with values

"phantom": {   
"strategy": "dedicated-process"

},
"tasks": {
"strategy": "dedicated-process"
},

Some details can be found here:
Reply all
Reply to author
Forward
0 new messages