Spring Boot连接AWS Redis集群报错：NoClassDefFoundError问题排查

Hey there, let's dig into this Spring Session + AWS Redis cluster issue you're facing. That BeanCreationException tied to the SessionProperties bean usually pops up when there's a misconfiguration or missing dependencies related to your Redis setup. Here are the most common fixes to try out:

Make sure your application.properties (or application.yml) has the correct AWS Redis cluster details—this is the most frequent culprit. You’ll need:

• spring.data.redis.cluster.nodes: Comma-separated list of your AWS Redis cluster nodes (format: host:port). AWS ElastiCache clusters have multiple nodes, so don’t skip any.
• spring.data.redis.password: Include this if your cluster uses password authentication (common if you enabled auth for ElastiCache).
• spring.session.store-type=redis: Explicitly set this to force Spring to use Redis for session storage.

Example application.yml snippet:

spring:
  data:
    redis:
      cluster:
        nodes: redis-cluster-001.your-aws-domain.com:6379,redis-cluster-002.your-aws-domain.com:6379
      password: your-redis-auth-password
  session:
    store-type: redis

Spring Session with Redis needs specific starters to work properly. Ensure your build file includes these:
For Maven (pom.xml):

<dependency>
    <groupId>org.springframework.boot</groupId>
    <artifactId>spring-boot-starter-data-redis</artifactId>
</dependency>
<dependency>
    <groupId>org.springframework.session</groupId>
    <artifactId>spring-session-data-redis</artifactId>
</dependency>

For Gradle:

implementation 'org.springframework.boot:spring-boot-starter-data-redis'
implementation 'org.springframework.session:spring-session-data-redis'

Missing either of these will leave Spring unable to find the classes needed to instantiate SessionProperties.

AWS ElastiCache clusters are typically hosted in a VPC, so your Spring Boot app needs proper network access:

• Ensure your app is in the same VPC as the Redis cluster, or has a VPC peering connection set up.
• Check security groups: The Redis cluster’s security group must allow inbound traffic on port 6379 (or your custom Redis port) from your app’s security group.
• If testing locally, you’ll need a bastion host or VPN to reach the VPC-based cluster—without this, connection failures can trigger indirect bean creation errors.

Spring Boot uses Lettuce as the default Redis client, which supports cluster mode out of the box. However:

• If you’ve manually overridden the Lettuce version, make sure it’s compatible with your AWS Redis cluster’s version.
• For Spring Boot 2.7+ or 3.x, the default Lettuce versions should work seamlessly with AWS ElastiCache, but double-check if you’ve made custom dependency changes.

If the above steps don’t resolve the issue, turn on debug logging to get the complete stack trace. Add this to application.properties:

logging.level.org.springframework.session=DEBUG
logging.level.org.springframework.data.redis=DEBUG

The full trace will reveal exactly what’s failing during SessionProperties instantiation—maybe a malformed property value, missing config, or underlying connection issue that’s being masked.

内容的提问来源于stack exchange，提问作者Daniel Haughton