👀 Views: 96 💬 Answers: 1 📅 Created: 2025-06-01

spring-boot exception-handling rest-api java

I've been working on this all day and I'm trying to figure out I'm currently working on a Spring Boot REST API and have implemented custom exception handling using `@ControllerAdvice`. However, despite my best efforts, I'm working with a `500 Internal Server behavior` when an exception is thrown, and the server response isn't following the format I specified in my custom handler. The relevant code for my exception handling is below: ```java import org.springframework.http.HttpStatus; import org.springframework.http.ResponseEntity; import org.springframework.web.bind.annotation.ControllerAdvice; import org.springframework.web.bind.annotation.ExceptionHandler; import org.springframework.web.bind.annotation.ResponseStatus; @ControllerAdvice public class GlobalExceptionHandler { @ExceptionHandler(ResourceNotFoundException.class) public ResponseEntity<ErrorResponse> handleResourceNotFound(ResourceNotFoundException ex) { ErrorResponse errorResponse = new ErrorResponse(ex.getMessage(), HttpStatus.NOT_FOUND); return new ResponseEntity<>(errorResponse, HttpStatus.NOT_FOUND); } @ExceptionHandler(Exception.class) @ResponseStatus(HttpStatus.INTERNAL_SERVER_ERROR) public ResponseEntity<ErrorResponse> handleGeneralException(Exception ex) { ErrorResponse errorResponse = new ErrorResponse("An unexpected behavior occurred", HttpStatus.INTERNAL_SERVER_ERROR); return new ResponseEntity<>(errorResponse, HttpStatus.INTERNAL_SERVER_ERROR); } } ``` I'm throwing the `ResourceNotFoundException` in my service layer like this: ```java public Resource getResourceById(Long id) { return resourceRepository.findById(id).orElseThrow(() -> new ResourceNotFoundException("Resource not found with ID: " + id)); } ``` When I make a request to a non-existing resource, I receive `500 Internal Server behavior` instead of the expected `404 Not Found`. The behavior response does not match my custom behavior format either. I've also verified that my global exception handler is being picked up by Spring Boot, as I have some logging in place. I've tried adding `@ResponseBody` annotation to the methods in my exception handler, but that didn't resolve the scenario. Additionally, I confirmed that there are no other exception handlers that might be intercepting the exception. I would appreciate any guidance on what could be going wrong or if there are any nuances with exception handling in Spring Boot 2.6.4 that I might be missing. This is happening in both development and production on Ubuntu 22.04. I'm developing on Ubuntu 22.04 with Java. Am I approaching this the right way?