Javax.validation验证失败返回500而非400的问题排查

项目中存在User实体，使用javax.validation实现字段级注解验证。当插入包含空值的用户数据时，系统返回500 Internal Server Error，但预期应返回400 Bad Request，需要处理该异常并返回合适的错误提示。

相关代码 #

实体类（Entity） #

public class User {

    @Id
    @GeneratedValue(strategy = GenerationType.AUTO)
    private Integer userId;
    
    @NotBlank(message = "Username should not be null !!")
    private String userName;
    
    @Email(message = "Email is not valid !!")
    private String email;
    
    @NotBlank(message = "Password should not be null !!")
    private String pasword;

    @NotBlank(message = "Please enter your contact number !!")
    private String contact;

}

控制器（Controller） #

@RequestMapping(value = "/", method = RequestMethod.POST)
public ResponseEntity<User> addUser(@Valid @RequestBody UserModel userModel){
    return ResponseEntity.ok(userService.addUser(userModel));
}

异常处理器（Exception Handler） #

@ExceptionHandler(MethodArgumentNotValidException.class)
@ResponseStatus(value = HttpStatus.BAD_GATEWAY)
public Map<String, String> handleMethodArgumentNotValidException(MethodArgumentNotValidException methodArgumentNotValidException) {
    Map<String, String> fieldException = new HashMap<>();

    methodArgumentNotValidException.getBindingResult().getAllErrors().forEach(e -> {
        fieldException.put(((FieldError) e).getField(), e.getDefaultMessage());
    });

    return fieldException;
}

报错信息 #

Postman返回内容 #

"timestamp": "2022-09-10T06:00:08.526+00:00",
    "status": 500,
    "error": "Internal Server Error",
    "trace": "org.springframework.transaction.TransactionSystemException: Could not commit JPA transaction; nested exception is javax.persistence.RollbackException: Error while committing the transaction\r\n\tat org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:571)\r\n\tat org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:743)\r\n\tat org.springframework.transaction.support.

Eclipse栈追踪信息 #

javax.validation.ConstraintViolationException: Validation failed for classes [com.hotel.booking.entity.User] during persist time for groups [javax.validation.groups.Default, ]
List of constraint violations:[
    ConstraintViolationImpl{interpolatedMessage='Please enter your contact number !!', propertyPath=contact, rootBeanClass=class com.hotel.booking.entity.User, messageTemplate='Please enter your contact number !!'}
]
    at org.hibernate.cfg.beanvalidation.BeanValidationEventListener.validate(BeanValidationEventListener.java:140) ~[hibernate-core-5.6.10.Final.jar:5.6.10.Final]
    ...（省略后续栈追踪内容）

1. 验证阶段错位：当前代码在Controller层对UserModel添加了@Valid注解做参数验证，但User实体上的JSR-380注解是在JPA持久化阶段（Hibernate执行insert操作时）才触发验证，此时抛出的是ConstraintViolationException，而非Controller层参数验证失败抛出的MethodArgumentNotValidException。
2. 异常处理器覆盖不全：现有的异常处理器仅处理了MethodArgumentNotValidException，未覆盖JPA抛出的ConstraintViolationException及其被事务封装后的TransactionSystemException，导致未捕获的异常触发500 Internal Server Error。
3. 状态码错误：现有异常处理器返回的HttpStatus.BAD_GATEWAY（502）不符合参数校验失败应返回400 Bad Request的HTTP规范。

方案1：补充异常处理器，覆盖所有相关异常 #

修改全局异常处理器，添加对ConstraintViolationException和TransactionSystemException的处理逻辑，返回标准400状态码和字段错误信息：

@RestControllerAdvice
public class GlobalExceptionHandler {

    // 处理Controller层参数验证异常
    @ExceptionHandler(MethodArgumentNotValidException.class)
    @ResponseStatus(HttpStatus.BAD_REQUEST)
    public Map<String, String> handleMethodArgumentNotValid(MethodArgumentNotValidException ex) {
        Map<String, String> errors = new HashMap<>();
        ex.getBindingResult().getAllErrors().forEach(error -> {
            String fieldName = ((FieldError) error).getField();
            String errorMessage = error.getDefaultMessage();
            errors.put(fieldName, errorMessage);
        });
        return errors;
    }

    // 处理JPA持久化阶段的验证异常
    @ExceptionHandler(ConstraintViolationException.class)
    @ResponseStatus(HttpStatus.BAD_REQUEST)
    public Map<String, String> handleConstraintViolation(ConstraintViolationException ex) {
        Map<String, String> errors = new HashMap<>();
        ex.getConstraintViolations().forEach(violation -> {
            String fieldName = violation.getPropertyPath().toString();
            String errorMessage = violation.getMessage();
            errors.put(fieldName, errorMessage);
        });
        return errors;
    }

    // 处理事务封装的异常，提取内部的ConstraintViolationException
    @ExceptionHandler(TransactionSystemException.class)
    @ResponseStatus(HttpStatus.BAD_REQUEST)
    public Map<String, String> handleTransactionSystemException(TransactionSystemException ex) {
        Throwable cause = ex.getRootCause();
        if (cause instanceof RollbackException && cause.getCause() instanceof ConstraintViolationException) {
            ConstraintViolationException violationException = (ConstraintViolationException) cause.getCause();
            return handleConstraintViolation(violationException);
        }
        Map<String, String> error = new HashMap<>();
        error.put("error", "Invalid request data");
        return error;
    }
}

方案2：提前在DTO层完成验证（推荐） #

如果UserModel是User实体的DTO，建议在UserModel上添加与实体一致的验证注解，确保在Controller层就拦截无效请求，避免到JPA阶段才抛出异常：

修改UserModel类 #

public class UserModel {
    
    @NotBlank(message = "Username should not be null !!")
    private String userName;
    
    @Email(message = "Email is not valid !!")
    private String email;
    
    @NotBlank(message = "Password should not be null !!")
    private String pasword;

    @NotBlank(message = "Please enter your contact number !!")
    private String contact;

    // getter、setter方法
}

确保从UserModel转换到User实体时字段值正确传递，这样Controller层的@Valid就能提前拦截无效请求，直接返回400错误。

额外修正 #

将现有异常处理器中的@ResponseStatus(value = HttpStatus.BAD_GATEWAY)改为HttpStatus.BAD_REQUEST，符合参数校验失败的HTTP状态码规范。

内容的提问来源于stack exchange，提问作者Faheem azaz Bhanej