Hi,

thanks for your reply and scrpits, I will test and get back with results.

we've given users the ability to create their own scheduled reports and also used the scripting capability for dynamic data gathering and email send. So when a schedule triggers, dynamic data is gathered from external API source and the report is sent after render via email. So, 100 users having 1-2 scheduled reports with their data sent on a daily basis would quickly pile up those numbers.

we've checked schedule history from time to time using the studio for debugging i.e. when a schedule fails to execute for some reason keeping error state. Being able to keep track of a certain # of instances for each schedule (i.e. last 5) via configuration would be helpful I suppose

Hello,

so I've managed to implement jsreport's scheduling component and allow users to create their own scheduled reports using API calls. Everything works and schedules are created/deleted normally for some time now.

What I noticed is an increased usage of storage disk on server, upon searching I found out that the 'tasks' file is now quite large (~70MB) and I think jsreport is reading/writing on it on a short periodical time. That causes the disk on server to be constantly occupied at around 2MB/s which is quite a load. I believe this file works as something of an 'instance keeper' for the schedules instances on jsreport.

My question: Is there a safe way to somehow unload this file without compromising the correct function of jsreport's scheduling component?

The problem seems to appear only on our production server (Windows Server 2016) when executing with the phantom-pdf recipe.

When running any pdf report with dummy data from jsReport studio, the Chinese characters are not rendered properly, they seem to be cut in half, not able to be dragged/copied by the cursor, like they are rendered as a picture and not as letters.

The error does not occur with html-to-xlsx recipe with the same data source file and also it does not occur at all on local machine (Windows 10 Pro), running the same jsReport project, using similar configuration files.
Examples of faulty (production server) and correct (local machine) exported pdf reports are attached (WeTransfer link).

I understand this could be a problem not related entirely to jsreport, as it's working properly on the local machine, but I haven't been able to find a solution for a long time, so any help would be much appreciated, thanks.

Exactly, I just wasn't looking at the right place, thanks a lot.

Hi there,
we're using jsreport's scheduling extension to create re-occurring rendering of our own created templates.

Each time a schedule is triggered, the template is filled with data drawn from our external API and the report is finally sent by email using an afterRender script.

Schedules are created via API with a post request on <SERVER_IP>/odata/schedules.

JSReport is currently running in production mode on our main on-premise server and also in development mode on our backup server ensuring that our system is up and running at all times.

Since JSReport saves schedules in memory (schedules, tasks files) we would like all schedules to be saved on the same (production) instance.

Is there a way to configure the disabling of the scheduling extension along with the rejection of above API call so that we ensure that no schedules are ever created on the development JSReport instance?

I found this thread about jsreport-freeze module, would the solution be as simple as installing the module and adding the freeze=true setting on schedules node in the config file?

Thanks

Reviving this thread since the problem seems more consistent now than before.
Link to the corrupted xlsx file: http://www42.zippyshare.com/v/Nczq0VhA/file.html

I'm bringing this thread back to ask about some issues I'm having with memory leaks on js report when I'm using the scheduling extension.

While stretch testing the extension, triggering multiple schedules at the same time I get 'FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory'
when I run more than about 50 schedules simultaneously. I'm suspecting the memory leak happening due to asynchronous requests, so schedules don't finish rendering reports while new requests are coming, consequently not releasing memory.

I've tried experimenting with the extension's maxParallelJobs and interval options with little results. My machine has 8gb of ram memory and I'm running jsreport with visual studio code debugger with development configuration

Is there an optimum configuration to avoid memory leaks as much as possible? Any advice in general would be appreciated, thanks.

OK, thanks a lot for the quick replies and support.

Any guidelines on how I could start implementing such a custom feature?
Maybe a way to temporarily update the schedule's nextRun, or cron fields?
Any info would be greatly appreciated, thanks!

Hi, thanks for the reply, really helpful.

"basically re-tries is part of the job of your scheduler"

I am indeed using jsreport's scheduling extension, can I do these re-tries internally?