quarkusio/quarkus · info · ResponseStatusException
bandwidth exceeded
Error message
bandwidth exceeded
What it means
responseStatusException throws Spring's ResponseStatusException with HttpStatus.BANDWIDTH_LIMIT_EXCEEDED (529) and reason 'bandwidth exceeded'. The test verifies Quarkus maps ResponseStatusException to the annotated HTTP status and reason string automatically, without a custom mapper.
Source
Thrown at integration-tests/spring-web/src/main/java/io/quarkus/it/spring/web/ExceptionThrowingController.java:78
@GetMapping("/pojo/pojo")
public Greeting pojoWithPojoException() {
throw new HandledPojoException("bad state");
}
@GetMapping("/pojo/void")
public void voidWithPojoException() {
throw new HandledPojoException("bad state");
}
@GetMapping("/string")
public String stringWithStringException() {
throw new HandledStringException("bad state");
}
@GetMapping("/responseStatusException")
public void responseStatusException() {
throw new ResponseStatusException(HttpStatus.BANDWIDTH_LIMIT_EXCEEDED, "bandwidth exceeded");
}
}
View on GitHub (pinned to e1c734241f)
Solutions
- Assert the client receives HTTP 529 and the 'bandwidth exceeded' reason; if not, check the RESTEasy Reactive version's ResponseStatusException handling.
- If you intended a different status, adjust the HttpStatus passed in the test or the test assertion.
- Confirm no custom mapper overrides ResponseStatusException handling in the test app.
Defensive patterns
Strategy: validation
Validate before calling
Response r = given().when().get("/exception/responseStatusException");
if (r.getStatusCode() != 529)
throw new AssertionError("ResponseStatusException status not honored: " + r.getStatusCode()); Prevention
- Prefer ResponseStatusException over custom mappers for simple status mapping
- Pin and test RESTEasy Reactive behavior after upgrades
- Document expected status codes in the test assertions
When it happens
Trigger: GET /exception/responseStatusException invokes responseStatusException which always throws ResponseStatusException(BANDWIDTH_LIMIT_EXCEEDED, "bandwidth exceeded").
Common situations: Appears when testing default ResponseStatusException handling; failures mean the framework no longer honors the status/reason, e.g. after a RESTEasy Reactive upgrade.
Related errors
- Parameter type <type> is being used multiple times in method
- Parameter type <type> is not supported for method<method> of
- Parameter type '<type>' is not supported for method '<method
- Spring Web can only work if 'quarkus-resteasy-jackson' or 'q
- @ExceptionHandler methods in @ControllerAdvice must be publi
AI-assisted analysis of quarkusio/quarkus@e1c734241f (2026-09-05).
Data as JSON: /api/errors/aed14e7322e73702.
Report an issue: GitHub.