Introduce better error code logging when DB connection error thread is raised so we can better understand the root cause of the stuck jobs issue or any other database connection errors.
Steps to Reproduce:
1. Run jobs as per recommended schedule on an environment experiencing database connection issues
2. Notice stuck jobs in Processing status for longer than 24 hours
3. Check the logs for the root cause
Expected Results: The logs to have the error code for the database disconnect
Actual Results: The logs do not have detailed information on the root cause
DE79684, fixed in 16.2.2 with the below changes:
Additional logging is in 16.2.2 release for better troubleshooting as follows:
Example:
Exception due to DB Connection failure 08001