Skip to content

Commit 5fd71b4

Browse files
authored
fix: Change log level of "A VaadinSession instance not associated to any service is getting unbound" (#13132) (#13140)
1 parent e236eb1 commit 5fd71b4

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

‎flow-server/src/main/java/com/vaadin/flow/server/VaadinSession.java‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -171,12 +171,12 @@ public void valueUnbound(HttpSessionBindingEvent event) {
171171
// {@link #refreshTransients(WrappedSession, VaadinService)}. It happens
172172
// when the session is deserialized and container decides that it's
173173
// expired. Such session is not known to anyone (except deserializer)
174-
// and nothins should be done with it: just return immediately.
174+
// and nothing should be done with it: just return immediately.
175175
//
176-
// Be aware that not initialized session doesn't have the
176+
// Be aware that a non-initialized session doesn't have the
177177
// correct/expected state: it has no lock, service, session, etc.
178178
if (!isInitialized()) {
179-
getLogger().warn(
179+
getLogger().debug(
180180
"A VaadinSession instance not associated to any service is getting unbound. "
181181
+ "Session destroy events will not be fired and UIs in the session will not get detached. "
182182
+ "This might happen if a session is deserialized but never used before it expires.");

0 commit comments

Comments
 (0)