- Newest
- Most votes
- Most comments
The error you're encountering during the automation step of the AWS Blu Age L3 workshop appears to be related to database schema conflicts and possibly some compatibility issues with Tomcat.
Here are some suggestions to resolve the issue:
-
Database Schema Conflict: The error "Schema "public" already exists" suggests that there might be a conflict with existing database objects. You may need to drop the existing schema or use a different schema name in your configuration.
-
Tomcat Version Compatibility: You mentioned using Tomcat version 10, which might be causing compatibility issues. The workshop may be designed for an earlier version of Tomcat. Try using Tomcat version 9.0.x instead, as it's known to be more compatible with the workshop environment. The newer version 10.0.x has changed some Java packages (from javax.servlet to jakarta.servlet) which could cause conflicts.
-
Check Configuration Files: Review your database configuration files (like application.properties or application.yml) to ensure they are set up correctly for the database you're using.
-
Verify Datasources: Double-check that all required datasources (jics, bluesam, bac, primary) are correctly configured in your Tomcat configuration files (context.xml and server.xml).
-
Synchronize Configurations: Run the Publish action on the Tomcat server to synchronize everything between the Eclipse WST working folder and the Tomcat configuration folder.
-
Clean Build: Try cleaning your project and rebuilding it from scratch. Sometimes, cached or stale build artifacts can cause unexpected errors.
If these steps don't resolve the issue, you may need to start the workshop again with a clean environment, ensuring you're using compatible versions of all components, particularly Tomcat and the database.
Remember to back up any important work before making significant changes to your environment.
Sources
AWS Blu Age L3 workshop - Automation step error | AWS re:Post
BluAge - L3 Workshop - org.hsqldb.HsqlException: type not found or user lacks privilege: BIGSERIAL | AWS re:Post
answered 2 years ago
Relevant content
asked 2 years ago
asked 2 years ago
