AWS BluAge L3 workshop. Go-Live-Deploy-Start application. Application fails to start.

Question

During Go-Live->Start application the application is deployed successfully but during Start application the application is failing with below error. i checked all configuration and everything looks good. Am i missing anything?

Caused by: 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]: Unsatisfied dependency expressed through method 'cacheProvider' parameter 0: Error creating bean with name 'cacheManager' defined in class path resource [com/netfective/bluage/bluesam/autoconfigure/BluesamAutoConfiguration$RedisBluesamAutoConfiguration.class]: Failed to instantiate [org.springframework.cache.CacheManager]: Factory method 'cacheManager' threw exception with message: Error creating bean with name 'bluesamRedisSerializer' defined in class path resource [com/netfective/bluage/bluesam/autoconfigure/BluesamAutoConfiguration$RedisBluesamAutoConfiguration.class]: Failed to instantiate [com.netfective.bluage.gapwalk.bluesam.redis.BluesamRedisSerializer]: Factory method 'bluesamRedisSerializer' threw exception with message: Error creating bean with name 'metadataPersistence' defined in class path resource [com/netfective/bluage/bluesam/autoconfigure/BluesamAutoConfiguration$PgsqlAutoConfiguration.class]: Failed to instantiate [com.netfective.bluage.gapwalk.bluesam.core.storage.MetadataPersistence]: Factory method 'metadataPersistence' threw exception with message: Error while trying to create the metadata table, using script

JaronRego · Accepted Answer

The issue was with the naming with one of the resource (database). it was not matching  (it was created with capital letters but inside the application it was all small letters) hence it was not reachable by the application, once renamed it worked. Thanks.

re:Post Agent · Answer

The error you're encountering during the "Start application" phase of the AWS BluAge L3 workshop's Go-Live process suggests there are issues with the application's dependency injection and bean creation, particularly related to the Redis cache and database configuration.

Here are some steps you can take to troubleshoot and potentially resolve the issue:

1. Check your Redis configuration: Ensure that the Redis server is running and accessible. Verify that the connection details (host, port, password if applicable) are correctly set in your application's configuration files.

2. Verify database configuration: The error mentions a problem with creating a metadata table. Double-check your database connection settings, including the URL, username, and password. Make sure the database server is running and accessible.

3. Review application properties: Examine your application.properties or application.yml file to ensure all necessary configurations for Redis, database, and other components are correctly set.

4. Check dependencies: Ensure that all required dependencies are present in your project's build file (pom.xml for Maven or build.gradle for Gradle) and that there are no version conflicts.

5. Examine logs: Look for more detailed error messages in the application logs. They might provide additional information about the specific cause of the failure.

6. Validate data sources: Ensure that all required data sources (jics, bluesam, bac, primary) are correctly configured and accessible.

If you've checked all these areas and the issue persists, you may need to reach out to the AWS BluAge L3 workshop support team for further assistance. They can provide more specific guidance based on the workshop's setup and requirements.

Remember that the workshop environment is designed to simulate real-world scenarios, so troubleshooting these issues is part of the learning process for achieving L3 certification.
      
**Sources**  
[AWS Blu Age L3 workshop - Automation step error | AWS re:Post](https://repost.aws/questions/QUEO1mQjRSR5afMPLkruEvsQ/aws-blu-age-l3-workshop-automation-step-error)  
[BluAge L3 Workshop (Go Live --> Testing --> Test Online) | AWS re:Post](https://repost.aws/questions/QUUdMPzUW5TSyIuhN3i6hjAA/bluage-l3-workshop-go-live-testing-test-online)

AWS BluAge L3 workshop. Go-Live->Deploy->Start application. Application fails to start.

Add your answer

Relevant content