why Its taking while adding the new transaction in Bluage L3 workshop?

When adding new transactions in the AWS Blu Age L3 workshop, several issues could cause delays or failures:

1. Program not found errors: You might be encountering a "Program not found: CEEDAYS" exception. This is a known issue in the workshop that can be resolved by adding stopExecutionWhenProgNotFound: false to your application-main.yml configuration file.

2. Database configuration issues: Ensure all your datasources (jics, bluesam, bac, primary) are correctly configured and accessible. Incorrect database connections can cause significant delays before ultimately failing.

3. Resource naming inconsistencies: Check that resource names (like databases) match exactly between your configuration and the actual resources. Mismatches in capitalization have caused issues for other workshop participants.

4. Data loading method: If you loaded data using the "local" method instead of the "server" method, this could corrupt records in the database due to incorrect record sizes. Try clearing the data and reloading it using the "server" method.

5. Server configuration: Verify that your Tomcat configuration files (context.xml and server.xml) are properly set up and that you've run the Publish action to synchronize everything between the Eclipse WST working folder and Tomcat configuration folder.

These issues can cause significant delays when processing transactions before ultimately failing. Addressing the specific configuration problem should resolve the performance issues.
Sources
BluAge L3 Workshop CEEDAYS Program not found Exception when adding new transaction online | AWS re:Post
AWS BluAge L3 workshop. Go-Live->Deploy->Start application. Application fails to start. | AWS re:Post
AWS Blu Age L3 Workshop - POSTTRAN execution problem | AWS re:Post
BluAge - L3 Workshop - org.hsqldb.HsqlException: type not found or user lacks privilege: BIGSERIAL | AWS re:Post