Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spring Session: Document different way to specify the session timeouts #357

Closed
ghillert opened this issue Apr 17, 2024 · 0 comments · Fixed by #384
Closed

Spring Session: Document different way to specify the session timeouts #357

ghillert opened this issue Apr 17, 2024 · 0 comments · Fixed by #384
Assignees
Labels
for: backport-to-3.3.x Marks an issue as a candidate for backport to 3.3.x

Comments

@ghillert
Copy link
Contributor

ghillert commented Apr 17, 2024

We should document the various ways to specify session timeouts (expiration of HTTP session entries in the respective Coherence cache). This should also include an explanation of the overriding behavior in case session expiration timeouts are specified in multiple locations:

  1. Setting the expiry via coherence-cache-config.xml

  2. In Spring boot using spring.session.timeout = 10m

  3. Via annotation @EnableCoherenceHttpSession(sessionTimeoutInSeconds = 5)

  4. By extending CoherenceHttpSessionConfiguration

  5. By declaring a SessionRepositoryCustomizer<CoherenceIndexedSessionRepository> bean:

@Bean
public static SessionRepositoryCustomizer<CoherenceIndexedSessionRepository> sessionRepositoryCustomizer() {
  return (sessionRepository) -> {
    sessionRepository.setDefaultMaxInactiveInterval(Duration.ofSeconds(120));
  };
}
@ghillert ghillert self-assigned this Jul 5, 2024
@ghillert ghillert added the for: backport-to-3.3.x Marks an issue as a candidate for backport to 3.3.x label Jul 5, 2024
ghillert added a commit to ghillert/coherence-spring that referenced this issue Jul 5, 2024
ghillert added a commit to ghillert/coherence-spring that referenced this issue Jul 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
for: backport-to-3.3.x Marks an issue as a candidate for backport to 3.3.x
Projects
None yet
1 participant