-
-
Notifications
You must be signed in to change notification settings - Fork 850
Fix SQL logging and add catch-all exception handler (continuation w #11988) #12004
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
nishantharkut
wants to merge
3
commits into
cBioPortal:master
from
nishantharkut:fix/11987-logging-and-catch-all
Closed
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
40 changes: 40 additions & 0 deletions
40
src/test/java/org/cbioportal/application/rest/error/GlobalExceptionHandlerTests.java
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,40 @@ | ||
| package org.cbioportal.application.rest.error; | ||
|
|
||
| import static org.assertj.core.api.Assertions.assertThat; | ||
|
|
||
| import java.sql.SQLException; | ||
| import org.junit.Test; | ||
| import org.springframework.http.HttpStatus; | ||
| import org.springframework.http.ResponseEntity; | ||
| import org.springframework.jdbc.BadSqlGrammarException; | ||
|
|
||
| public class GlobalExceptionHandlerTests { | ||
|
|
||
| private final GlobalExceptionHandler handler = new GlobalExceptionHandler(); | ||
|
|
||
| @Test | ||
| public void handleBadSqlGrammarReturnsInternalServerError() { | ||
| BadSqlGrammarException ex = | ||
| new BadSqlGrammarException("task", "SELECT 1", new SQLException("bad sql")); | ||
|
|
||
| ResponseEntity<ErrorResponse> response = handler.handleBadSqlGrammar(ex); | ||
|
|
||
| assertThat(response.getStatusCode()).isEqualTo(HttpStatus.INTERNAL_SERVER_ERROR); | ||
| assertThat(response.getBody()).isNotNull(); | ||
| assertThat(response.getBody().getMessage()) | ||
| .isEqualTo( | ||
| "SQL exception. If you are a maintainer of this instance, see logs for details."); | ||
| } | ||
|
|
||
| @Test | ||
| public void handleUncaughtExceptionReturnsInternalServerError() { | ||
| RuntimeException ex = new RuntimeException("something unexpected"); | ||
|
|
||
| ResponseEntity<ErrorResponse> response = handler.handleUncaughtException(ex); | ||
|
|
||
| assertThat(response.getStatusCode()).isEqualTo(HttpStatus.INTERNAL_SERVER_ERROR); | ||
| assertThat(response.getBody()).isNotNull(); | ||
| assertThat(response.getBody().getMessage()) | ||
| .isEqualTo("An unexpected error occurred. Please contact your administrator."); | ||
| } | ||
| } |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ExceptionHandler(Exception.class)will also intercept Spring MVC framework exceptions (e.g.,HttpRequestMethodNotSupportedException,HttpMediaTypeNotSupportedException, etc.) that would otherwise be translated to correct 4xx/405 responses by Spring’s default resolvers. With this catch-all in place, those cases may start returning a generic 500ErrorResponseinstead. Consider narrowing the handler toRuntimeException(to avoid overriding framework 4xx handling) and/or adding explicit handlers for common Spring MVC exceptions with appropriate HTTP statuses, or extendingResponseEntityExceptionHandlerto preserve the default mappings while still returning JSON.