Dependency-Track returns 500.

The defect may already be reported! Please search for the defect before creating one.

### Current Behavior:
When I navigate to a project, https://[URL]/dependency-track/project/?uuid=[UUID], and wait a minute, I will get a pop-up window with the following "An unexpected error occurred. Please contact the Dependency-Track administrator for assistance (500)."
There is nothing in the tomcat or Dependency-Track logs (using the default logging levels).
Using the browser developer tools it looks as if the following API call is the issue: https://[URL]/dependency-track/api/v1/finding/project/[UUID]?searchText=&sortOrder=asc
The response from this request is "{"message": "An error occurred. Please try again."}
Also, the Overview and Dependencies tabs seem to be populated just fine, but the Audit tab is empty.

### Steps to Reproduce:
See Above.

### Expected Behavior:

### Environment:

- Dependency-Track Version: 3.7.1
- Distribution: Traditional WAR
- BOM Format & Version: Cyclone DX, most current.
- Database Server: MySQL - AWS RDS.
- Browser: IE, Chrome, Mozilla.

### Additional Details:
I can provide screen shots if necessary.
This began occurring after an upgrade to the latest version and a move from the H2 DB to an AWS MySQL instance.

(e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

Start by reproducing the failure on the project page in Dependency-Track 3.7.1 and inspect the browser request to /dependency-track/api/v1/finding/project/[UUID]?searchText=&sortOrder=asc. Compare the behavior with the MySQL AWS RDS setup after the H2 migration and review the available Tomcat and Dependency-Track logs. Done means the request no longer returns 500 and the Audit tab is populated.

Written by the indexing model from the issue text.