Uploaded image for project: 'RESTEasy'
  1. RESTEasy
  2. RESTEASY-1758

Microprofile OpenTracing error handling - wrong status code in servlet filter on exceptions thrown from handler

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • jaxrs
    • None

      Hi,

      we are working on Microprofile OpenTracing spec. I wanted to consult how is it possible to log all or just unmapped exceptions in Resteasy.

      At the moment we are using jax-rs filter which starts monitoring object (span) and servlet filter with finishes it. In Jersey this filter it is possible to catch unmapped exceptions[1], however in resteasy exception is not propagated to the filter.

      Can somebody explain how we can log these exceptions?

      [1] :https://github.com/opentracing-contrib/java-jaxrs/pull/54/files#diff-c690d43efd9d019cc50b8aec5440ce42R54

      UPDATE:
      If an exception is thrown in handler status code in servlet filter is wrong e.g. 200 and should be 500. Microprofile-TCK test this so we need some adjustments on RESTEasy side.

            weli@redhat.com Weinan Li
            ploffay@redhat.com Pavol Loffay
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: