BluAge L3 Workshop (Go Live --> Test application)

The null pointer exception you're encountering during the batch testing phase of the BluAge L3 Workshop could be related to several factors, but it's unlikely to be caused solely by using PostgreSQL 13.20.

Here are some potential causes and solutions to consider:

1. Database configuration: Ensure that your database connection details are correctly set in the application configuration files. This includes verifying the URL, username, password, and any other relevant parameters.

2. Data integrity: Although you mentioned that your database includes all the data, double-check that the specific tables and records required for the batch jobs are present and correctly formatted.

3. Application properties: Review your application.yml or application.properties file to confirm all necessary configurations are present and correct, especially those related to database access and batch processing.

4. Bluesam configuration: Verify that the Bluesam configuration, particularly the database secret manager ARN, is correctly set in the application definition.

5. Permissions: Ensure that the application has the necessary permissions to access the database and execute the batch jobs.

6. Restart services: Try restarting the Tomcat server or the entire workshop environment to ensure all components are in a clean state.

7. Check logs: Examine the application logs for more detailed error messages that might provide additional context about the null pointer exception.

If the issue persists after checking these points, you may need to review the specific batch job configurations and the code handling the database interactions. It's also worth noting that in some cases, users have resolved similar issues by refreshing their browser or switching to a different version of Tomcat (e.g., from Tomcat 9 to Tomcat 10).

If you continue to experience problems, consider reaching out to the workshop facilitators or AWS BluAge support for more specific guidance, as there might be workshop-specific configurations or requirements that need to be addressed.
Sources
BluAGE L3 workshop issue with Go-Live Test batches and Online | AWS re:Post
L3 Workshop - Go Live - Test Online - Transaction not Found | AWS re:Post