Tags: Abuchtela/flow
Tags
chore: Log the Spring Framework version (vaadin#16631) (vaadin#16633) Co-authored-by: Artur <artur@vaadin.com>
chore: Log the Spring Framework version (vaadin#16631) (vaadin#16634) Co-authored-by: Artur <artur@vaadin.com>
chore!: Remove the themeModule concept (vaadin#16568) Simplifies code as the concept is no longer needed now that both Lumo and Material always prepend their styles to `<head>`, no matter at which point they are loaded.
fix: prevent deadlock on concurrent push disconnection (vaadin#16544) (… …vaadin#16582) If the AtmospherePushConnection.disconnect method is invoked concurrently by multiple threads, a deadlock may happen if the servlet container somehow locks HTTP session, as closing AtmosphereResource may cause accesses to the HTTP session. For example, is a thread (A) is invalidating the HTTP session, thus closing Vaadin UIs and disconnecting push, and another thread (B) is also requesting a push disconnect, then B will be blocked when closing the atmosphere resource by the lock on the session held by A, but A is actually waiting to acquire the lock on AtmospherePushConnection held by B, causing the deadlock. This change allows a single thread to perform the disconnect operation, to avoid potential deadlocks. Fixes vaadin#16293
fix: prevent deadlock on concurrent push disconnection (vaadin#16544) (… …vaadin#16582) (vaadin#16585) If the AtmospherePushConnection.disconnect method is invoked concurrently by multiple threads, a deadlock may happen if the servlet container somehow locks HTTP session, as closing AtmosphereResource may cause accesses to the HTTP session. For example, is a thread (A) is invalidating the HTTP session, thus closing Vaadin UIs and disconnecting push, and another thread (B) is also requesting a push disconnect, then B will be blocked when closing the atmosphere resource by the lock on the session held by A, but A is actually waiting to acquire the lock on AtmospherePushConnection held by B, causing the deadlock. This change allows a single thread to perform the disconnect operation, to avoid potential deadlocks. Fixes vaadin#16293 Co-authored-by: Marco Collovati <marco@vaadin.com>
fix: prevent deadlock on concurrent push disconnection (vaadin#16544)… … (CP: 9.1) (vaadin#16579) If the AtmospherePushConnection.disconnect method is invoked concurrently by multiple threads, a deadlock may happen if the servlet container somehow locks HTTP session, as closing AtmosphereResource may cause accesses to the HTTP session. For example, is a thread (A) is invalidating the HTTP session, thus closing Vaadin UIs and disconnecting push, and another thread (B) is also requesting a push disconnect, then B will be blocked when closing the atmosphere resource by the lock on the session held by A, but A is actually waiting to acquire the lock on AtmospherePushConnection held by B, causing the deadlock. This change allows a single thread to perform the disconnect operation, to avoid potential deadlocks. Fixes vaadin#16293
fix: use OS path separator in stats plugin (vaadin#16559) The StatsPlugin uses an hard-coded forwars slash charachter to split the file identifier in path segments. This produces wrong results when running on Windows, as the identifier contains back slashes. This change uses node 'path.sep' as split chars Fixes vaadin#16234
fix: use OS path separator in stats plugi 3FF0 n (vaadin#16559) (vaadin#16566) The StatsPlugin uses an hard-coded forwars slash charachter to split the file identifier in path segments. This produces wrong results when running on Windows, as the identifier contains back slashes. This change uses node 'path.sep' as split chars Fixes vaadin#16234 Co-authored-by: Marco Collovati <marco@vaadin.com>
PreviousNext