Monitoring SonarQube

  • Enterprise Edition Version 7.9.3

  • We are currently using JMX mbeans to monitor our service.

  • We have updated file as mentioned here.
    Restarted sonarqube. Initially we were seeing issue when trying to use same jmx port for web and compute engine both. I believe this could be because once the web is activated , the port are already occupied.
    so currently we have this configuration in for web -

and for compute engine we have-

sonar.ce.javaOpts=-Xmx2G -Xms128m -XX:+HeapDumpOnOutOfMemoryError

where the jmxremote password and access file are same as described in the documentation .

After bringing up the SonarQube successfully, i could see the corresponding ports are occupied. But not sure how to check jconsole here. I tried running jconsole in the jdk bin but it was coming as blank. It would be really helpful if anyone can suggest me here.

Hi Amisha

Please note that SonarQube v8.9 is now the minimum supported version of SonarQube. You should consider an upgrade at your earliest convenience.

You are following the right instructions and appears it you have SonarQube watching for remote JMX connections.

Usually jconsole hostName:portNum will bring up a list of processes on the host, but JConsole is not the best tool for troubleshooting connections. For more about how to use Oracle’s JConsole, see their Monitoring and Management Using JMX Technology.

The open source project VisualVM (the “All-in-One Java Troubleshooting Tool”) may give you better UI and logs, to diagnose what is going on.