L3 Workshop - Go Live - Test Online - Transaction not Found
After deploying and starting my application in AWS M2, I tested the batches previously mentioned in the workshop (Test Batches) which ran succesfully, but upon trying to open the online view, I enter 'CC00' transaction and I get a 'Transaction not found' error as seen in the screenshot below, and got no errors in the logs:
Link to workshop section: https://catalog.us-east-1.prod.workshops.aws/workshops/bf71c0bc-6d8a-4d04-9c10-ab479f7f0e37/en-US/go-live/test/online
- Newest
- Most votes
- Most comments
The issue came from the initJics.sql file being located in a wrongly named folder that was uploaded to S3. Didn't have it under artifacts/jics/sql/initJics.sql
The 'Transaction not found' error you're encountering is often an indication that the database table is empty or not properly configured. Here are some steps you can take to troubleshoot and resolve this issue:
-
Check your database configuration: Ensure that your database is set up correctly according to the workshop documentation. This includes verifying the connection details and table structures.
-
Verify data presence: Query the database manually to confirm if it contains the necessary data. The error suggests that the required transaction information might be missing.
-
Review application properties: Double-check your application.yml or application.properties file to ensure all database-related configurations are correct, including the data source settings for jics, bluesam, bac, and primary.
-
Examine logs: Look for any database-related errors in your application logs that might provide more insight into the issue.
-
Refresh the browser: In some cases, simply refreshing the browser page has resolved this issue for other users.
-
Check Tomcat version: Ensure you're using the correct version of Tomcat. Some users have reported success by switching to Tomcat 10 instead of Tomcat 9 for the carddemo-automation project.
-
Verify BluAge engine version: Confirm that you're using the correct version of the BluAge engine as specified in the workshop.
If these steps don't resolve the issue, you may need to review the batch jobs that were run earlier to ensure they populated the database correctly. If the problem persists, consider opening a support case with AWS for more specialized assistance, as some details required to fully diagnose the issue may involve non-public information.
Sources
BluAge L3 Workshop (Go Live --> Testing --> Test Online) | AWS re:Post
BluAge L3 Workshop (Go Live --> Testing --> Test Online) Blank Screen when testing Online Transactions CC00 | AWS re:Post
BluAGE L3 workshop issue with Go-Live Test batches and Online | AWS re:Post
Relevant content
- asked 8 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 months ago
