24.2. RESTEasy Built-in Internally-Thrown Exceptions


RESTEasy has a set of built-in exceptions that are thrown when an error is encountered during dispatching or marshalling. Each exception matches a specific HTTP error code. The full list is available in the RESTEasy Java Documentation, under the org.jboss.resteasy.spi package. The following table lists the most common exceptions:
Expand
Table 24.1. Common Exceptions
Exception HTTP Code Description
BadRequestException 400 Bad Request. Request was not formatted correctly or there was a problem processing request input.
UnauthorizedException 401 Unauthorized. Security exception thrown if you use RESTEasy's simple annotation- and role-based security.
InternalServerError Exception 500 Internal Server Error.
MethodNotAllowed Exception 405 Method Not Allowed. There is no JAX-RS method for the resource that can handle the invoked HTTP operation.
NotAcceptableException 406 Not Acceptable. There is no JAX-RS method that can produce the media types listed in the Accept header.
NotFoundException 404 Not Found. There is no JAX-RS method that serves the request path/resource.
Failure N/A Internal RESTEasy. Not logged.
LoggableFailure N/A Internal RESTEasy error. Logged.
DefaultOptionsMethod Exception N/A If the user invokes HTTP OPTIONS without a JAX-RS method, RESTEasy provides a default behavior by throwing this exception.
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat