| Dropped Sessions [message #1695524] |
Fri, 15 May 2015 13:24  |
Eclipse User |
|
|
|
My team is using RAP 2.3, and experiencing issues with dropped sessions. When 15-30 clients are connected, we routinely get 5-10 sessions dropped in the span of about three hours due to timeout (HTTP 403) or request counter inconsistency (HTTP 412). In investigating the RAP codebase, those are returned explicitly by the LifeCycleServiceHandler due to protocol state violations. The application was originally in RCP, uses the Workbench, and is quite heavy with widgets. It also uses a session-long ServerPush to manage many Display async execs that occur due to user interactions being reflected in the other clients.
My question is what are the conditions in which the request counter would get out of sync with such high frequency? Also, we have seen an active client make requests within seconds of receiving a session timeout. Perhaps this is due to some browser pre-fetch or caching issue, but we are not sure why this occurs either. Any help would be appreciated.
--Paul Bilnoski
|
|
|
| Re: Dropped Sessions [message #1696006 is a reply to message #1695524] |
Thu, 21 May 2015 02:57  |
| Eclipse User |
|
|
|
Hi Paul,
the only case (I'm aware of), when the request counter could go out of
sync is when using BrowserFunction intensively. As BrowserFunction is
the only component in RAP that uses synchronous request, it's possible
an asynchronous request sent during the pending synchronousto leads of
messed request counter. This issue is fixed in RAP 3.0 as request
counter is not incremented on the server anymore, but on the client.
HTH,
Ivan
--
Ivan Furnadjiev
..
Twitter: @EclipseRAP
Blog: http://eclipsesource.com/blogs/
Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
|
|
|
Powered by
FUDForum. Page generated in 0.03015 seconds
Home