Ask Your Question

Revision history [back]

There may be several reasons why the listener is not registered in Spring-Boot when using Spring-Session (Redis) and HttpSessionListener. Some possible reasons are:

  1. The listener class is not properly registered in the Spring configuration. Make sure that the listener is registered through the @Component or @Bean annotation or by configuring it in the application.properties file.

  2. There may be a conflict between the Spring-Session and HttpSessionListener configuration. In this case, you may need to modify the Spring-Session configuration to adjust its behavior or customize its behavior to work with the HttpSessionListener.

  3. There may be a mismatch between the Spring version and the Spring-Session version. Check if the versions of the two frameworks are compatible and compatible with the deployed application server.

  4. There may be a problem with the Redis cache configuration. Check if the Redis configuration is properly set and Redis is properly running and accessible.