Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-20040

npm package metadata requests that return 200 status code and error body should be logged

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: 3.16.0, 3.16.1, 3.16.2
    • Fix Version/s: 3.17.0
    • Component/s: Logging, NPM

      Description

      During load testing of npm package metadata requests, in rare cases it was noticed that NXRM may return a HTTP status code of 200 and a response body indicating an error - that "bug" and its diagnosis is being tracked at NEXUS-20171.

      In such a scenario, there are no expected WARN level error messages on the NXRM server side nexus.log indicating this problem happened. The exception that triggered the error is ignored.

      It is important to log this condition. Exceptional conditions should never be completely ignored.

      Expected

      *In such a case, the exception should be logged at least at WARN level with blob/asset details. If DEBUG level is set for the logger doing the logging, then include the stack trace.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              moncef Moncef Ben-Soula
              Reporter:
              plynch Peter Lynch
              Last Updated By:
              Peter Lynch Peter Lynch
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Date of First Response:

                  tigCommentSecurity.panel-title