Print Job Timeout after 60s -- where do I increase the timeout setting?
So, we know about (and have enabled) the asynchronous "Print Job" setting in the Rest Manager, but are still getting a timeout error. This is almost certainly a resource issue... the error only occurrs when we've loaded large data into the viewer (how much data depends on the machine running the app) and have a high resolution defined (in this case 288 dpi). Obviously, the quickest solution to the problems here is to reduce load on the client; we understand that but still want to allow a bit more time for the viewer to chew before it gives up.
Currently, it takes 60 seconds to timeout. We've tried editing the executiontimeout property in the httpRuntime tag in the web.config files for the REST and GVH directories to no avail... does anyone know where we need to make a change to give ourselves more time here? I see that the default executionTimeout value is 110 seconds on server 2012 (which we're running) so am wondering whether we may actually be encountering a different roadblock entirely.
Thank you for your help, I'm feeling pretty discombobulated on this one.
0
-
Hi Zack,
The Geocortex Viewer for HTML5 has a 60-second timeout on any web request. If it's taking longer than 60 seconds for the viewer to send the print request to Essentials, even for an asynchronous job, then I think you are hitting the limits of what we can expect the viewer to be able to do.
The best solution is to find a better way to load your data into the viewer so it doesn't have to manage and transfer so much, thus staying away from the 60-second request timeout. If you can't do that, you can increase the timeout; this may resolve your issue or it may just reveal another component that is timing out (or assuming that the process has hung)..
Information on increasing the viewer timeout is in this KB article:
https://support.geocortex.com/essentialsGSCkba?sub-nav=kba&main-nav=essentials&#!/feedtype=SINGLE_ARTICLE_DETAIL&criteria=BESTANSWERS&id=kA360000000XbYWCA00
Du måste logga in om du vill lämna en kommentar.
Kommentarer
1 kommentar