AWS Builder Center is the official home for builders on AWS. Share and read what others are working on, follow people who inspire you, explore training and workshops, and find tools to support what you're building.
Unable to connect to Redis server while starting carddemo application
After starting the application (as part of L3 workshop), its failing with "Unable to connect to Redis server" error. I am unable to find the root cause of this. Can anyone help me on this pelase ?
I am getting following error :
org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'applicationInitializer': Unsatisfied dependency expressed through field 'bluesamManager': Error creating bean with name 'com.netfective.bluage.bluesam.autoconfigure.BluesamAutoConfiguration$EmbeddedBluesamAutoConfiguration': Unsatisfied dependency expressed through field 'cacheProvider': Error creating bean with name 'cacheProvider' defined in class path resource [com/netfective/bluage/bluesam/autoconfigure/BluesamAutoConfiguration$RedisBluesamAutoConfiguration.class]: Failed to instantiate [com.netfective.bluage.gapwalk.bluesam.core.storage.CacheProvider]: Factory method 'cacheProvider' threw exception with message: Error creating bean with name 'redissonClient' defined in class path resource [com/netfective/bluage/bluesam/autoconfigure/BluesamAutoConfiguration$RedisBluesamAutoConfiguration.class]: Failed to instantiate [org.redisson.api.RedissonClient]: Factory method 'redissonClient' threw exception with message: Unable to connect to Redis server: aws-bluage-l3-workshop-redis-bk2.vcns5j.ng.0001.euc1.cache.amazonaws.com/10.0.154.33:6379
- Newest
- Most votes
- Most comments
The error you're encountering suggests that your application is unable to establish a connection with the Redis server. This is a common issue in the AWS BluAge L3 workshop and can be caused by several factors. Here are some steps you can take to troubleshoot and resolve the issue:
-
Verify Redis endpoint: Double-check that the Redis endpoint (aws-bluage-l3-workshop-redis-bk2.vcns5j.ng.0001.euc1.cache.amazonaws.com) is correct and accessible from your application's network.
-
Check security group rules: Ensure that the security group associated with your application allows outbound traffic to the Redis server on port 6379.
-
Validate network connectivity: Confirm that there are no network issues preventing communication between your application and the Redis server.
-
Review Redis configuration: Check your application's configuration files (like application.yml or application.properties) to ensure the Redis connection details are correctly specified.
-
Verify Redis server status: Make sure the Redis server is running and healthy in AWS ElastiCache.
-
Check for firewall restrictions: Ensure no firewalls are blocking the connection to the Redis server.
-
Examine ElastiCache setup: In AWS ElastiCache, when creating the Redis cache, make sure you've selected "Design your own cache" and then "Cluster cache" instead of "Serverless".
If you've checked all these areas and the issue persists, you may need to review your application's Redis client configuration more thoroughly. Sometimes, the problem can be as simple as a typo in a configuration file or a mismatch between the expected and actual Redis cluster setup.
Remember, troubleshooting these issues is part of the learning process in the L3 workshop. If you continue to face difficulties, don't hesitate to reach out to the AWS BluAge L3 workshop support team for more specific guidance.
Sources
Troubleshoot error messages in ElastiCache Redis clients | AWS re:Post
Error ‘BluesamManager’ when starting modernized application in AWS Mainframe Modernization | AWS re:Post
AWS BluAge L3 workshop. Go-Live->Deploy->Start application. Application fails to start. | AWS re:Post
answered a year ago
Relevant content
asked 10 months ago
Somehow the security group was removed from the redis server (aws-bluage-l3-workshop-redis-bk2). I have added them now and its working fine now.