Solved

Smartobject call that takes up to 6 minutes to return result gives issues in browser console


Hi, 

 

I have a smartobject call that can take quite a long time to be finished. (it slices a PDF file into images and zips this on the server). Logically the size of the PDF will directly influence the duration of the smo call. We have come across a file that takes just under 6 minutes for the server to process and thus for the smo to return its properties. That is not an issue in itself. When I execute through the smartobject tester, I get the return properties after the estimated 6 minutes. But in the browser I get errors in the console. Already after a minute or two I get the first errors, which keep repeating themselves after every minute or so. The redlined error appears when the server is finished (CPU goes back to idle, files are created). The view spinner just keeps on spinning and the rule execution has come to a stop. When I do the exact same thing with a smaller PDF, it all works just fine. 

 

Does anybody have experience with issues like this (which appear to be some kind of time out setting) and how to fix them?

10880i3833B2E72B1CF183.jpg

icon

Best answer by MdenHeijer 26 August 2019, 10:24

View original

2 replies

Hi  @MdenHeijer;


 


Please take a look at this few suggestions:-


-Clear browser cache---observ


-Do iisreset-observ


-For time-out adjustment settings, please check out this kb(https://help.k2.com/support-services/kbt133195)


-For smartform perfomance isssue please dive into this kb(https://help.k2.com/support-services/kbs100015)


-Also checkout what smartobject logs gives you(https://help.k2.com/kb000298)


 


Hope your issue will get resolved.


 


Kind regards;


Widson.

Hi Widson,

 

Thanks for your support. We have found the issue. The web.config file contains an executionTimeout setting. This was the bottleneck.

 

<httpRuntime maxRequestLength="131072" requestValidationMode="2.0" enableVersionHeader="false" sendCacheControlHeader="false" executionTimeout="3200" />

Reply