Uploaded image for project: 'Nuxeo Platform'
  1. Nuxeo Platform
  2. NXP-28560

Failed enrichers cause exception to be thrown as response

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 10.10-HF20, 11.1-SNAPSHOT
    • Fix Version/s: 10.10-HF22, 11.1
    • Component/s: Rest API

      Description

      Currently when any of the enrichers fails the exception is thrown as response thus preventing access to anything else (body, other enrichers, etc..).

      Regardless of enricher failures the request itself should not fail, so, as a first step, we will simply:

      • catch any enricher error
      • not include the failed enrichers in the answer (=> no contexParameters entry for that enricher)

      This would allow clients to have access to the response while still being able to know which (if any) enricher failed (with logs visible on the server, no client side error reporting on enrichers for now).

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 2 days
                  2d

                    PagerDuty

                    Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.