Hello,
We’ve seen this several times now and cant figure out why the application does this.
For example – we have a desktop type application – even closing a window sometimes causes the never-ending spinning to happen and it never recovers -it will sit there forever. Pressing F5 to refresh the browser recovers it and its back to normal. The operations like closing a window are not time intensive.
Any Ideas ?
Hi Edmond,
The settings in default.json are all preset to their default values as documented in the json itself and here: https://wisej.com/docs/html/Configuration.htm. You don’t need to change “enableWebSocket” unless you want to turn it off.
The spinning ajax loader is displayed after “loaderTimeout” milliseconds if the browser doesn’t receive a response from the server. I think the default is too short, it should be set to 3 or 5 seconds I think. If you have it “stuck” and you are in debug with VS attached to IIS, just push pause in VS and see if there is anything running in your app. It is also possible that there is a mismatch of responses or a javascript error that prevents Wisej from turning off the loader – especially since hitting F5 works fine it makes me thing the server is not busy at all.
The warnings you attached are all not from Wisej, they are coming from the mozilla pdfjs, which has an ajax spinning loader of its own. They all seem harmless warnings. When using Chrome console you get a lot of stuff logged that can be ignored – in fact most of the web pages around will give you a ton of javascript errors when you use the console.
Also try (as a test) to increase the session timeout to a higher value (which will reduce the keepalive messages) and see if the issue is resolved. In previous builds the keepalive message was session-synchronized and could have caused the spinner to show by itself (it has been changed to an async message).
HTH – Let me know.
Hi Edmond,
all seems to be fine.
Next, you can try to add a trace listener and log the informations coming from Wisej.
You can use this web.config entry descibed here.
Best,
Jens
Screenshot attached of Developer console in Chrome
Hi Edmond,
when you open the developer tools from your browser, are there any erros/exceptions displayed in the console?
Which Wisej Version are you using? You can also see it in developer tools: Sources – … – resources.wx — Wisej.Web – wisej.js?v=1.5.xx
Are there any changes in default.json related to responseTimeout or showLoader?
Can you please specify more cases where this happens?
Best,
Jens
Please login first to submit.