Hi all,
In the Web Client we are getting often strange issues - the UI will “freeze” with the “Loadng…” indicator displayed. Users need to hit the browser Refresh button to get the application going again. There are no errors in the log on the server and everything else works as expected before and after the refresh. It seems as if the browser is not receiving the expected ajax response from the server however everything seems fine on the server side. What might be causing this issue and are there any suggestions on how to resolve it?
Thanks in advance for your help!
you could try to monitor the requests, and see what happens with the request that are Loading…
jcompagner:
you could try to monitor the requests, and see what happens with the request that are Loading…
The problem is that nothing happens - the request is over but the page never “acknowledges” that it has received the response and the UI is blocked as if it is still waiting for the response from the server.
The issue happens mostly for clients connecting to the server over a higher-latency network connections (for example, 300ms which is typical for the south-east Asia connections)
Another issue which perhaps is related to this one and also happens only on the higher-latency networks - when the focus is currently in a field and the user clicks on another field or button, the “Loading” indicator is displayed for a while and then disappears, the original field has lost its focus but the field which the user has clicked on never receives the focus (or if the user has clicked on a button, the button action is never invoked). The user needs to click a second time to complete the operation which they intended to do in the first place. The issue happens even if there are no callbacks hooked to any of the events of the fields or the form. Again, as if the web client completely looses what actually triggered the ajax call in the first place - in these cases however the “Loading” indicator disappears but the frustrated user has to click again on the field/button.
if you somehow have a sample where this happens quite often, please make a case with that sample
I can fake a latency in code (just sleeping for all request .5 seconds on the server at the moment they are coming in)
You could also test/do this your self if you want by creating a very simple Tomcat/Servlet Filter that captures all requests, sleeps first and then sends it through.
I have clients that report the same problem, and I have randomly experienced it myself (and I have a fast connection). Its like it just gets disconnected, but I can’t reliably reproduct it.