- Newest
- Most votes
- Most comments
This was an issue with the carddemo_bluesam bluesam database having a - in the name instead of a _. It is resolved.
It looks like a a dependency issue here, Could you check class the following property in catalina.properties
common.loader="${catalina.base}/lib","${catalina.base}/lib/*.jar","${catalina.home}/lib","${catalina.home}/lib/*.jar","C:/Bluage/workshop/CardDemo/Runtime-Timebomb/shared","C:/Bluage/workshop/CardDemo/Runtime-Timebomb/shared/*.jar"
The Tomcat server is unable to start due to an error in creating a bean for the Bluesam component, which is part of the AWS Blu Age Runtime. Specifically, there's an issue with creating the metadata table for the Bluesam manager.
The error message indicates that there's a problem with the database configuration or connectivity. It seems that the application is trying to create a metadata table using a script, but this operation is failing.
This could be due to several reasons:
- The database server might not be running or accessible.
- The database credentials in the configuration might be incorrect.
- The user specified in the database configuration might not have sufficient permissions to create tables.
- There could be an issue with the database schema or existing tables.
To resolve this, you should:
- Verify that the database server is running and accessible from the EC2 instance where Tomcat is installed.
- Double-check the database configuration in the application-main.yml file, ensuring that the connection details (host, port, database name, username, and password) are correct.
- Make sure the database user has the necessary permissions to create tables and modify the schema.
- Check the database logs for any specific errors that might provide more details about the failure.
If the issue persists, you may need to manually create the required metadata table or review the SQL script that's failing to execute. Additionally, enabling debug mode as suggested in the error message could provide more detailed information about the problem.
Sources
Set up configuration for AWS Blu Age Runtime - AWS Mainframe Modernization
AWS Blu Age L3 workshop - Automation step error | AWS re:Post
BluAge L3 Workshop CEEDAYS Program not found Exception when adding new transaction online | AWS re:Post
Relevant content
- asked 2 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 3 years ago
Here is my param in common.loader... Note my shared files are in the location as specified below. common.loader="${catalina.base}/lib","${catalina.base}/lib/.jar","${catalina.home}/lib","${catalina.home}/lib/.jar","C:/Work/AWS-BluAge/Runtime-Timebomb/shared","C:/Work/AWS-BluAge/Runtime-Timebomb/shared/*.jar"