dbMe1

Thanks for trying to help. AFAIK I am not using any reverse proxy, and as I said, it is not something that I can reproduce at-will. I realize this makes...

I am wondering if maybe it could be related to network latency and if so... if there might be some vaadin setting that I could configure to help ensure it...

It just happened again 2023-12-20T22:46:16.011Z ERROR 7 --- [dbME] [nio-6386-exec-3] c.v.flow.server.DefaultErrorHandler : @replica: 8176016e-94a8-4e52-8b46-0b5ccb4161c3 java.lang.UnsupportedOperationException: Unexpected message id from the client. Expected sync id: 3, got 4. more details logged...

upon closer examination I see that the call to authContext.logout() is already killing the session for me (which is what I would expect anyway). So I suppose the issue has...

this appears to be the same elusive issue reported here: https://github.com/vaadin/flow/issues/16664 surely you guys can catch this and do something to have the client and server sides get synced up...

I will need to keep testing, but after about 1 hour of testing it appears that I may have just fixed this issue by sidestepping it... by removing this code...