As a follow-up of this conversation, we need to add a test for the REST API that verifies that SQLExceptions with SQLState=08XXX (connection errors) that occur during a REST call will be logged as ERRORS.
The test should have the following structure:
Given a REST API Call (e.g list groups) that performs a query to the db
When a db connection error occurs
Then the logging of that exception should take place using ERROR Logging level
Hints
See org.camunda.bpm.engine.rest.exception.ExceptionLogger & the handling of ProcessEnginePersistenceException
This ticket should be treated as technical debt for covering the REST API's logging of db connection problems with an automated test.
It can be developed as soon as the linked feature is merged to master
Acceptance Criteria (Required on creation)
As a follow-up of this conversation, we need to add a test for the REST API that verifies that
SQLException
s withSQLState=08XXX
(connection errors) that occur during a REST call will be logged as ERRORS.Hints
See
org.camunda.bpm.engine.rest.exception.ExceptionLogger
& the handling ofProcessEnginePersistenceException
Links
Breakdown
Dev2QA handover