Mon 13:41:11 GMT+1000 (Australian Eastern Standard Time) Atmosphere: unload event Logger.js?aa4d:46 workbox Using NetworkOnly to respond to '/' Logger.js?aa4d:46 workbox Network request for '/' returned a response with status '200'. Logger.js?aa4d:46 workbox Router is responding to: / logger.js?aa4d:46 workbox The navigation route / is being used. Which is immediately followed with the page reloading. VaadinPush.js?v=23.0.4:3323 Websocket closed normally VaadinPush.js?v=23.0.4:3323 Mon 13:41:09 GMT+1000 (Australian Eastern Standard Time) Atmosphere: Request already closed, not firing onClose (closed case) VaadinPush.js?v=23.0.4:3323 Websocket closed, reason: Normal closure the connection successfully completed whatever purpose for which it was created. VaadinPush.js?v=23.0.4:3323 Mon 13:41:09 GMT+1000 (Australian Eastern Standard Time) Atmosphere: websocket.onclose close() on WebSocket objectįlowClient.js?2d7e:193 Processing time was 5ms VaadinPush.js?v=23.0.4:3323 Mon 13:41:09 GMT+1000 (Australian Eastern Standard Time) Atmosphere: invoking. VaadinPush.js?v=23.0.4:3323 Mon 13:41:09 GMT+1000 (Australian Eastern Standard Time) Atmosphere: Request already closed, not firing onClose (unsubscribe case)
VaadinPush.js?v=23.0.4:3323 Mon 13:41:09 GMT+1000 (Australian Eastern Standard Time) Atmosphere: Firing onClose (unsubscribe case)įlowClient.js?2d7e:1006 Push connection closed VaadinPush.js?v=23.0.4:3323 Mon 13:41:09 GMT+1000 (Australian Eastern Standard Time) Atmosphere: Closing (AtmosphereRequest._close() called) VaadinPush.js?v=23.0.4:3323 Mon 13:41:09 GMT+1000 (Australian Eastern Standard Time) Atmosphere: beforeunload eventįlowClient.js?2d7e:193 Setting heartbeat interval to -1sec.įlowClient.js?2d7e:835 Disabling heartbeatįlowClient.js?2d7e:936 Closing push connection Received push (websocket) message: for( ) įlowClient.js?2d7e:1004 Handling message from serverįlowClient.js?2d7e:944 Handling dependenciesįlowClient.js?2d7e:193 handleUIDLMessage: 0 ms Here is the Chrome console as the Session terminates. Suggestions for further diagnostics, or just an outright solution (I can dream) would be greatly appreciated. This appears (to me) to be initiated in the browser, possibly by the service worker? There is nothing indicating why this is going on in the java logs. When the VaadinSession timeout happens, the page automatically reloads starting a new VaadinSession.īelow, I have included the Chrome console log as the session ends and the reload happens.
0 kommentar(er)
