[MAGNOLIA-5899] Accelerate heartbeat of vaadin client synchronization request Created: 28/Aug/14 Updated: 12/Mar/15 Resolved: 28/Aug/14 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | bundle |
| Affects Version/s: | 5.3.2 |
| Fix Version/s: | 5.3.3 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Eric Hechinger | Assignee: | Eric Hechinger |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Release notes required: |
Yes
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
UI that are open on the client side send a regular heartbeat to the server to indicate they are still alive, even though there is no ongoing user interaction. When the server does not receive a valid heartbeat for a given UI, it will eventually remove that UI from the session. By default, heartbeats are sent every five minutes, and the server closes an UI after three missed heartbeats. This is done in the web.xml by setting the heartbeatInterval value
<context-param>
<param-name>heartbeatInterval</param-name>
<param-value>90</param-value>
</context-param>
https://vaadin.com/book/vaadin7/-/page/application.lifecycle.html |
| Comments |
| Comment by Jan Haderka [ 28/Aug/14 ] |
|
What is the impact of this change on network traffic and server cpu load? |
| Comment by Aleksandr Pchelintcev [ 28/Aug/14 ] |
|
Heartbeat request is super-light request that Vaadin UI client-side sends to server just to let it know it's alive, so the impact should be neglectable. I would though set the value to something a bit less frequent like 60-90 seconds so that those requests for instance do not clutter the dev tools. |
| Comment by Philip Mundt [ 29/Aug/14 ] |
|
Increase heartbeatInterval to 90 seconds. |