ExecutionAbortedException
Exception thrown when the server stops a statement before it finishes - a statement_timeout, or a cancel request such as session.cancelQuery() (57014).
What ends is the statement, not the session: the server abandons it, reports this, and the connection goes on to the next one. Inside a transaction the transaction is doomed as after any other error, until it is rolled back. A timeout that ends the session itself - transaction_timeout, idle_in_transaction_session_timeout, idle_session_timeout - is SessionTerminatedException instead, since there the connection goes too.
Parameters
The SQL state code returned by the database.
The original error message from the database server.
Properties
Where this happened, innermost first, appended to by each layer as the exception unwinds. It is on the base class for the same reason queryContext is: adding to it is the only thing a frame can do to an exception without replacing it, and replacing one costs the type the caller catches on - a ConstraintViolationException restated as something else stops being the failure a retry looks for. A mapper walking a nested composite appends the attribute it was on, a transaction plan the step and parameter it was resolving. Rendered reversed, outermost first, so PATH: step 1 -> parameter 'name' -> map #1 reads from the plan down to the lambda.
The context of the query that resulted in this exception, if applicable.
The raw error message received from the database, if applicable.