Skip to content

AWS Blu Age L3 workshop -Automation Build Failed

0

Hello, Facing error on automation step for L3 workshop. Step Link -https://catalog.us-east-1.prod.workshops.aws/workshops/bf71c0bc-6d8a-4d04-9c10-ab479f7f0e37/en-US/automation/execute

After checking the status of various setups and tool installations, I started the DB server and executed Ant Build for execute.xml, but the following 5 errors were output and it failed. Automation execution Build error command prompt output “ERROR: Schema "public" already exists” is thought to be the cause. But I have no idea to solve this.

The following has been confirmed Environment: tomcat is ver.10 from zip file ・DB server is started and running correctly. ・Automation Settings(Import project/Configure projects/Package application/Copy WAR files/Configure Tomcat/Configure automation project) are correctly set up.

asked 2 years ago254 views

1 Answer
1
Accepted Answer

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:

  1. 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.

  2. 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.

  3. 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.

  4. 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).

  5. Synchronize Configurations: Run the Publish action on the Tomcat server to synchronize everything between the Eclipse WST working folder and the Tomcat configuration folder.

  6. 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

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.