Catch the exception type the claim conflict actually throws

Shipped: August 7, 2026 at 7:19 AM UTC
Author: Kamo
Commit: f64b5c2

Round 2 review fix: the statement-level 40001 (the common case, detected inside executeUpdate() rather than at commit) surfaces as **************** via Hibernate's ExceptionConverterImpl, not as a Spring ConcurrencyFailureException. SupportTicketService is @Service, not @Repository, so nothing translates it on the way out. The controller now catches both types; the commit-time ConcurrencyFailureException path (the rarer case) still works as before. Split the round-1 serialization test in two so both surfacing paths are pinned instead of one Spring-only type standing in for both.

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free Forever View Pricing