You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: spring-session-docs/src/docs/asciidoc/guides/boot-websocket.adoc
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,14 +59,14 @@ What does `AbstractSessionWebSocketMessageBrokerConfigurer` do behind the scenes
59
59
60
60
* `WebSocketConnectHandlerDecoratorFactory` is added as a `WebSocketHandlerDecoratorFactory` to `WebSocketTransportRegistration`.
61
61
This ensures a custom `SessionConnectEvent` is fired that contains the `WebSocketSession`.
62
-
The `WebSocketSession` is necessary to terminate any WebSocket connections that are still open when a Spring Session is terminated.
62
+
The `WebSocketSession` is necessary to end any WebSocket connections that are still open when a Spring Session is ended.
63
63
* `SessionRepositoryMessageInterceptor` is added as a `HandshakeInterceptor` to every `StompWebSocketEndpointRegistration`.
64
64
This ensures that the `Session` is added to the WebSocket properties to enable updating the last accessed time.
65
65
* `SessionRepositoryMessageInterceptor` is added as a `ChannelInterceptor` to our inbound `ChannelRegistration`.
66
66
This ensures that every time an inbound message is received, that the last accessed time of our Spring Session is updated.
67
67
* `WebSocketRegistryListener` is created as a Spring bean.
68
68
This ensures that we have a mapping of all of the `Session` IDs to the corresponding WebSocket connections.
69
-
By maintaining this mapping, we can close all the WebSocket connections when a Spring Session (HttpSession) is terminated.
69
+
By maintaining this mapping, we can close all the WebSocket connections when a Spring Session (HttpSession) is ended.
70
70
71
71
72
72
// end::config[]
@@ -131,7 +131,7 @@ You can see that the message is no longer sent.
131
131
====
132
132
Spring Session expires in 60 seconds, but the notification from Redis is not guaranteed to happen within 60 seconds.
133
133
To ensure the socket is closed in a reasonable amount of time, Spring Session runs a background task every minute at 00 seconds that forcibly cleans up any expired sessions.
134
-
This means you need to wait at most two minutes before the WebSocket connection is terminated.
134
+
This means you need to wait at most two minutes before the WebSocket connection is closed.
All JDBC operations in `JdbcIndexedSessionRepository` are executed in a transactional manner.
1181
-
Transactions are executed with propagation set to `REQUIRES_NEW` in order to avoid unexpected behavior due to interference with existing transactions (for example, running a `save` operation in a thread that already participates in a read-only transaction).
1180
+
All JDBC operations in `JdbcIndexedSessionRepository` are performed in a transactional manner.
1181
+
Transactions are performed with propagation set to `REQUIRES_NEW` in order to avoid unexpected behavior due to interference with existing transactions (for example, running a `save` operation in a thread that already participates in a read-only transaction).
0 commit comments