bug #7035: Vaadin views keeping connection open as long as the view has not exited
correctly release vaadin view resources when the browser windows has been closed
ref #7036 implementing DetachListener in DistributionStatusUI to relase db connections for unused Views
ref #7036 LoginView in View scope helps disposing this bean
it is no longer required to have it in the UIScope
#14 Updated by Andreas Kohlbecker 11 months ago
the problem seems mainly to be caused by the
NavigationManagerBean not releasing the references to
RegistrationWorksetViewBeans contained in
currentView and by the
PopupViewRegistration keeping the
RegistrationWorksetViewBean in the
popupViewFieldMap where its used as key.
#15 Updated by Andreas Kohlbecker 11 months ago
Resources which are still in memory after closing a browser window should be destroyed automatically once the next heardbeat has reached the server.
It is defined by the
5.8.5. UI Expiration
UI instances are cleaned up if no communication is received from them after some time. If no
other server requests are made, the client-side sends keep-alive heartbeat requests. A UI is
kept alive for as long as requests or heartbeats are received from it. It expires if three consecutive
heartbeats are missed.
heartbeatInterval is at 5 minutes (300 seconds) per default.
#16 Updated by Andreas Kohlbecker 11 months ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 50
Applied in changeset cdm-vaadin|b14494a9c3be6a70f64c4560209ba8d406eb635f.
#17 Updated by Andreas Kohlbecker 11 months ago
- Status changed from Resolved to Closed
- Target version changed from Release 5.5 to Release 5.4
- % Done changed from 50 to 100
now all spring beans like RegistrationToolbar, RegistrationUI, RegistrationWorkingsetPresenter, NavigationManagerBean are disposed when the session times out due to inactivity.