Uploaded image for project: 'SonarQube'
  1. SonarQube
  2. SONAR-8338

JMX and RMI logs level should individually controlled by a property

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 6.2
    • Component/s: None
    • Labels:

      Description

      When trace logs are enabled, logs related to consumption of JMX metrics exposed by the SonarQube JVMs is responsible for 999 log lines out of 1000 on sonarqube.com.
      These log lines are produced by various loggers and depend on the frequency and number of calls to JMX counters.

      Here is a the list of loggers which have been grepped out by ops to be able to read TRACE logs on sonarqube.com :

      • javax.management.remote.timeout
      • javax.management.remote.misc
      • javax.management.remote.rmi
      • javax.management.mbeanserver
      • sun.rmi.loader
      • sun.rmi.transport.tcp
      • sun.rmi.transport.misc
      • sun.rmi.server.call
      • sun.rmi.dgc

      Property sonar.log.level.web.jmx is added and allows to control the log level of loggers sun.rmi.* and javax.management.*.

      The level of the most accurate and defined property among sonar.log.level.web.jmx, sonar.log.level and sonar.log.level.web must be applied.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                sebastien.lesaint Sebastien Lesaint
                Reporter:
                sebastien.lesaint Sebastien Lesaint
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Due:
                  Created:
                  Updated:
                  Resolved: