|
| Re: Timeout with mobile devices [message #1838146 is a reply to message #1838131] |
Wed, 17 February 2021 12:54   |
|
Hi Nils,
first of all, thank you for sharing your use case. A Scout app running on a barcode scanner sounds interesting :)
If I were you I would try to increase the log level and also add some more log output to trace the request. If you set the log level of the org.eclipse.scout.rt.ui.html module to debug, the requests processed by the UIServlet will be logged.
According to your description the request to send the value of the string field to the UI server is blocked. Every request initiated by the Scout UI has a unique correlation id that will be included in the requests from the UI server to the backend as well. With some well placed log statements you should be able to see how far the request goes.
You should also check the http session timeouts which are usually set in the web.xml of the .war modules. Maybe it can help to use the same timeout for the backend server as for the UI server. What timeouts do you currently use?
If the http session timeout of the UI server expires, the user will be logged out. To make sure inactive users are not logged out too early, the poller keeps the session alive until scout.ui.maxUserIdleTime is reached. In your case, since the device is going to sleep, the poller won't be active anymore so the session won't be kept alive actively. But if the http session of the UI server expires, a session timeout message should appear rather than a "please wait popup".
Best regards
Claudio
|
|
|
|
| Re: Timeout with mobile devices [message #1838236 is a reply to message #1838215] |
Fri, 19 February 2021 08:16 |
|
Are you sure that the request is not being processed by the UI server when the please wait popup appears? Normally, if there is a connection loss, Scout goes into offline mode and starts a Reconnector that regularly pings the UI server trying to reconnect. During that time the reconnect notification is shown.
In your case, the browser either does not notice the connection loss or the request is stuck in the UI server. Can you reproduce this behavior with a regular smart phone? If I disable the wifi or put my smartphone on flight mode it correctly goes into offline mode and reconnects as soon as I enable regular mode again.
Scout does not use a timeout for regular requests because they could possibly last very long (e.g. if the processing really takes some time). If you want you can change it by adjusting the default ajax options. To do so you need to extend the Session.js class and override the method defaultAjaxOptions. Please see the technical guide to learn how to replace the default Session class using the object factory: https://eclipsescout.github.io/8.0/technical-guide-js.html#object-factory
This behavior has not been changed for Scout 10 and 11.
|
|
|
|
Powered by
FUDForum. Page generated in 0.03901 seconds
] 
Search
Help
Register
Login
Home
