Default Exception Mapper Related Question

[Subrhamanya]

I migrated my application from jersey 2.x to 3.x along with spring boot. Previously when I throw any RuntimeException, the errors will be mapped to MappableException class and processed. But after migration to 3.1.8, it seems the exceptions are not mapped properly and I can see the error log org.glassfish.jersey.server.ServerRuntime$Responder - An exception mapping did not successfully produce and processed a response. Logging the exception propagated to the default exception mapper. java.lang.IllegalArgumentException: Invalid format: " "

Is there any other way to implement it or is it a bug?

cc: @jansupol

[Subrhamanya]

Logs for jersey 2.x application

Message: Starting mapping of the exception.

• Throwable: org.glassfish.jersey.server.internal.process.MappableException: java.lang.UnsupportedOperationException: This Operation is unsupported by the underlying implementation. Error code= 611
  at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.mapTargetToRuntimeEx(AbstractJavaResourceMethodDispatcher.java:185)
  at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.access$200(AbstractJavaResourceMethodDispatcher.java:52)
  at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:155)
  at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:167)
  at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$TypeOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:219)
  at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:79)
  at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:475)
  at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:397)
  at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:81)
  at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:255)
  at org.glassfish.jersey.internal.Errors$1.call(Errors.java:248)
  at org.glassfish.jersey.internal.Errors$1.call(Errors.java:244)
  at org.glassfish.jersey.internal.Errors.process(Errors.java:292)
  at org.glassfish.jersey.internal.Errors.process(Errors.java:274)
  at org.glassfish.jersey.internal.Errors.process(Errors.java:244)
  at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:265)
  at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:234)
  at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:684)
  at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:394)
  at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:346)
  at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:366)
  at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:319)
  at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:205)

[Subrhamanya]

jersey 3.x application

An exception mapping did not successfully produce and processed a response. Logging the exception propagated to the default exception mapper.
java.lang.UnsupportedOperationException: This Operation is unsupported by the underlying implementation. Error code= 611
org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory.lambda$static$0(ResourceMethodInvocationHandlerFactory.java:52)
at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:146)
at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:189)
at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$TypeOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:219)
at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:93)
at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:478)
at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:400)
at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:81)
at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:274)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:248)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:244)
at org.glassfish.jersey.internal.Errors.process(Errors.java:292)
at org.glassfish.jersey.internal.Errors.process(Errors.java:274)
at org.glassfish.jersey.internal.Errors.process(Errors.java:244)
at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:266)
at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:253)
at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:696)
at org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:394)
at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:346)
at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:358)
at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:312)
at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:205)

[Subrhamanya]

Note: Starting mapping of the exception doesn't happen in jersey 3.x

[senivam]

as per 3.1 RESTful API requirement each implementation must have a default exception mapper:

A JAX-RS implementation MUST include a default exception mapping provider that implements ExceptionMapper<Throwable> and which SHOULD set the response status to 500.

The 3.1.x versions of Jersey respect that requirement, so exceptions are handled by the default exception mapper.

If the default behavior does not meet your needs, you can implement a custom exception mapper, which would process exceptions as required by your application.