Home/ Questions/Q 9201785
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-17T23:06:08+00:00

My technology stack is Tomcat (servlet 3.0), Jersey for JAX-RS, Spring and Hibernate. When

  • 0

My technology stack is Tomcat (servlet 3.0), Jersey for JAX-RS, Spring and Hibernate. When something unexpect goes wrong like some data conversion error in Hibernate, I do not want the clients to see my stacktrace for those exceptions that the Tomcat tries to print by default. However I would like to log those exceptions so I can find what is wrong and fix things.

My first try was using ExceptionMapper from JAX-RS and naively thinking that would solve my problems. But then I noticed that Jersey throws it’s own exceptions for example urls that are not mapped are com.sun.jersey.api.NotFoundExceptions. This causes 404 exceptions to be logged which I don’t want. Worse, the client no longer gets 404 but a status code 500.

I could just create exception mappers for the exceptions that jersey throws but I could miss something. Is there a best practice for something like this?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    All exceptions thrown directly by Jersey are subclasses of WebApplicationException, so if you want to catch them all just create an ExceptionMapper for that class and you’ll be good.

    • 0