Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-10805

Reduce the log level of "User with id [...] does not exist" exception

    XMLWordPrintable

Details

    Description

      Steps to reproduce

      1. Make a rest request for a user account that does not exist (e.g. /user/<id>/profile

      Observed behavior

      • Server log contains the following exception on level warning: 
         org.camunda.bpm.engine.rest.exception.InvalidRequestException: User with id [...] does not exist
	at org.camunda.bpm.engine.rest.sub.identity.impl.UserResourceImpl.getUserProfile(UserResourceImpl.java:56)

      Expected behavior

      • As this is an expected exception and the error is also communicated via the HTTP status code and error message, it is sufficient to log the exception on a lesser severity level, e.g. FINE

      Side notes

      • E.g. we could decide the log level based on the http response code, e.g. 5xx is always logged on WARNING, where all other status codes are logged on FINE
      • Consider defining a proper logger name and documenting the purpose of this logger
      • Make sure to check all exception handlers

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Issue Links

            depends on

            Task - A task that needs to be done. CAM-10923 Move Logging Rule to Camunda Commons

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Closed
            is related to

            Feature Request - A new feature of the product, which has yet to be developed. CAM-3614 improve tunability of REST exception logging

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Closed

            Activity

              People

                Unassigned Unassigned
                ilias.kourtoudis Ilias
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce