Project

General

Profile

bug #7036

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

Added by Andreas Kohlbecker about 1 year ago. Updated about 2 months ago.

Status:
Closed
Priority:
Highest
Category:
cdm-vaadin
Target version:
Start date:
10/25/2017
Due date:
% Done:

100%

Severity:
normal
Found in Version:
Tags:

picture893-1.png View (56.7 KB) Andreas Kohlbecker, 10/23/2018 04:57 PM


Related issues

Related to Edit - bug #7046: replace open session per view pattern by DTO strategy Closed 11/02/2017
Related to Edit - bug #6687: Multiple representations of the same entity merge problem Closed 06/02/2017
Related to Edit - bug #7047: Vaadin UI and View scope beans are not always destroyed correctly Closed 11/02/2017

Associated revisions

Revision 948d9990 (diff)
Added by Andreas Kohlbecker about 1 year ago

ref #7036 implementing DetachListener in DistributionStatusUI to relase db connections for unused Views

Revision 7e488d1b (diff)
Added by Andreas Kohlbecker about 1 year ago

ref #7036 disposing resources in mvp beans

Revision 157c9c3d (diff)
Added by Andreas Kohlbecker about 1 year ago

ref #7036 LoginView in View scope helps disposing this bean
it is no longer required to have it in the UIScope

Revision b14494a9 (diff)
Added by Andreas Kohlbecker about 2 months ago

fix #7036 making sure all spring beans are disposed when the vaadin session times out
- RegistrationToolbar, RegistrationUI, RegistrationWorkingsetPresenter, NavigationManagerBean as DisposableBean
- seetting the vaadin closeIdleSessions parameter to true in web.xml

History

#1 Updated by Andreas Kohlbecker about 1 year ago

  • Related to bug #7047: Vaadin UI and View scope beans are not always destroyed correctly added

#2 Updated by Andreas Kohlbecker about 1 year ago

  • Related to deleted (bug #7047: Vaadin UI and View scope beans are not always destroyed correctly)

#3 Updated by Andreas Kohlbecker about 1 year ago

  • Duplicated by bug #7047: Vaadin UI and View scope beans are not always destroyed correctly added

#4 Updated by Andreas Kohlbecker about 1 year ago

  • Description updated (diff)
  • Status changed from New to In Progress

#5 Updated by Andreas Kohlbecker about 1 year ago

  • Tags set to phycobank
  • Priority changed from Highest to Priority13
  • Target version changed from Release 4.11 to Reviewed Next Major Release
  • Severity changed from blocker to normal

#6 Updated by Andreas Kohlbecker about 1 year ago

  • Related to bug #7046: replace open session per view pattern by DTO strategy added

#7 Updated by Andreas Kohlbecker about 1 year ago

  • Related to bug #6687: Multiple representations of the same entity merge problem added

#8 Updated by Andreas Kohlbecker about 1 year ago

  • Subject changed from correctly release vaadin view resources when the browser windows has been closed to correctly release vaadin view ad UI resources

#9 Updated by Andreas Kohlbecker about 1 year ago

  • Duplicated by deleted (bug #7047: Vaadin UI and View scope beans are not always destroyed correctly)

#10 Updated by Andreas Kohlbecker about 1 year ago

  • Related to bug #7047: Vaadin UI and View scope beans are not always destroyed correctly added

#11 Updated by Andreas Kohlbecker about 1 year ago

  • Subject changed from correctly release vaadin view ad UI resources to correctly release vaadin view resources when the browser windows has been closed
  • Description updated (diff)

#12 Updated by Andreas Kohlbecker about 2 months ago

  • Priority changed from Priority13 to Highest
  • Target version changed from Reviewed Next Major Release to Release 5.5

it seems as this is not yet solved.

#13 Updated by Andreas Kohlbecker about 2 months ago

after editing in parallel with 3 users for some time and closing all browser tabs afterwards, some spring beans like the LoginPresenter and the RegistrationWorkingsetPresenter and View are not disposed:

#14 Updated by Andreas Kohlbecker about 2 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 about 2 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 @VaadinServletConfiguration.InitParameterName(value="heartbeatInterval"):

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.

The heartbeatInterval is at 5 minutes (300 seconds) per default.

#16 Updated by Andreas Kohlbecker about 2 months ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 50

#17 Updated by Andreas Kohlbecker about 2 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.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 40 MB)