BluAge Self-Paced Workshop - Execution Backend: Tomcat Server is failing to start

The error you're encountering with Tomcat v10.0 failing to start during the "Execution - Backend" step of the AWS Blu Age L3 Workshop is likely due to a version compatibility issue.

Based on similar issues reported in the workshop, the problem may be related to:

1. Tomcat version incompatibility: The workshop appears to be designed for Tomcat 9.0.x, not Tomcat 10.0.x. In version 10.0.x, Java packages changed from javax.servlet to jakarta.servlet, which can cause compatibility issues with the workshop applications.

2. Database-related errors: There might be issues with the database configuration, particularly with data types like BIGSERIAL that aren't supported in HSQLDB.

Here are some suggested solutions:

1. Try replacing Tomcat 10.0.x with Tomcat 9.0.x, which should be more compatible with the workshop environment.

2. Check that all required datasources (jics, bluesam, bac, primary) are correctly configured in your Tomcat configuration files (context.xml and server.xml).

3. Run the Publish action on the Tomcat server to synchronize everything between the Eclipse WST working folder and the Tomcat configuration folder.

4. Review your database configuration files to ensure they're set up correctly for the database you're using.

If these steps don't resolve the issue, you might need to check the Tomcat logs for more specific error messages that could provide additional clues about what's causing the startup failure.
Sources
BluAge - L3 Workshop - org.hsqldb.HsqlException: type not found or user lacks privilege: BIGSERIAL | AWS re:Post
AWS Blu Age L3 workshop -Automation Build Failed | AWS re:Post
AWS Blu Age L3 workshop - Automation step error | AWS re:Post