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 ?
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.
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.
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?
Please login first to submit.