Topics created by pardonmeme

...use markdown formatting...

Yes nothing to do with jsreport.
It is well known IIS behavior that it after some idle time recycles application pool and put it to sleep.
Search for azure web app "always on" option.

Thanks "face palm"

hi!

And I made a small thing like that with express, but the problem that I have when I deployed in on azure windows web app with node >=8.9 is that making request to
the endpoint which takes used the jsreport-core, it hangs up for 2 minutes and then just timesout. I don't know, maybe my setup is wrong or maybe the jsreport core is using some different ports?

i don't see anything that looks bad with your code, however maybe the problem is related to azure limitations with phantom, you can find here another user that discover a problem and fixed by changing the azure plan, maybe you can try that.

So you call StartAsync() every time you want to render a report?
You should do it just once. During the application init for example.

Got a new error after cleaning and building again

I can imagine it would be so slow if you use some kind of micro instance in azure.
However on local computer. If you run "Hello world". It should be done always in less than a second.

This is mentioned in docs.
https://jsreport.net/learn/dotnet-local#custom-extensions

The binary includes just default extensions from the jsreport v1. So there is no wkhtmltopdf or chrome.
You can install wkhtmltopdf but chrome won't work with v1 binary.

There are pre-release binaries for jsreport.Local jsreport.binary... which includes compiled jsreport v2 version that have the chrome by default.
You can try it out.

I would like to know what is timing out.
I am not an azure web app user. However it should be possible to get the container output logs.
I think it is something that was accessible from portal ui.
If not you should be able to connect to the instance with "shell" and run docker logs xxxx I guess.