GlobalDefaultExceptionHandler异常message缺失具体异常信息

[youngzil]

• 我已经检查过discussions
• 我已经搜索过issues
• 我已经仔细检查过FAQ

描述bug

1. 在前台批量修改时，如果有一个注释太长，超过了数据库的长度，最终得到的返回报文如下，缺失了最根本的报错信息

{
    "exception": "org.springframework.dao.DataIntegrityViolationException",
    "message": "could not execute statement; SQL [n/a]; nested exception is org.hibernate.exception.DataException: could not execute statement",
    "status": 500.0,
    "timestamp": "2025-03-26T15:04:11.69"
}

2. 通过后台代码可以看出来，

   apollo/apollo-common/src/main/java/com/ctrip/framework/apollo/common/controller/GlobalDefaultExceptionHandler.java

   Line 118 in 6657a58

   String message = ex.getMessage();

实际实现是 org.springframework.core.NestedRuntimeException#getMessage，只处理了2层包装异常

3. 缺失了最根本的message ：Data too long for column 'Comment' at row 1
   

复现
通过如下步骤可以复现：

期望

简介明了地描述你希望正常情况下应该发生什么

截图

如果可以，附上截图来描述你的问题

额外的细节和日志

• 版本：
• 错误日志
• 配置：
• 平台和操作系统

[dosubot]

To address the issue of missing root cause messages in the GlobalDefaultExceptionHandler for DataIntegrityViolationException, you can enhance the exception handling to include deeper nested exception messages. Here's a suggested approach:

1. Modify the Exception Handler: Add a specific handler for DataIntegrityViolationException that extracts the root cause message.

@ExceptionHandler(DataIntegrityViolationException.class)
public ResponseEntity<Map<String, Object>> handleDataIntegrityViolationException(
    HttpServletRequest request, DataIntegrityViolationException ex
) {
  Throwable rootCause = ex.getRootCause();
  String rootCauseMessage = rootCause != null ? rootCause.getMessage() : ex.getMessage();
  return handleError(request, BAD_REQUEST, new BadRequestException(rootCauseMessage));
}

This code snippet retrieves the root cause of the exception using ex.getRootCause() and extracts its message. If the root cause is not available, it defaults to the exception's message. This message is then used to create a BadRequestException, which is passed to the handleError method to generate the error response ^[1].

2. Ensure Proper Logging: Make sure that the logging mechanism captures the full stack trace and root cause messages for better debugging and traceability.

By implementing these changes, the error response should include the detailed message "Data too long for column 'Comment' at row 1," providing clearer feedback on the nature of the database constraint violation.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}