SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • ShellShell
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
Java

Java static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your JAVA code

  • All rules 733
  • Vulnerability60
  • Bug175
  • Security Hotspot40
  • Code Smell458

  • Quick Fix 65
Filtered: 10 rules found
sustainability
    Impact
      Clean code attribute
        1. Bluetooth should be configured to use low power

           Code Smell
        2. Motion Sensor should not use gyroscope

           Code Smell
        3. Use Fused Location to optimize battery power

           Code Smell
        4. Use batch Processing in JDBC

           Code Smell
        5. Constant parameters in a "PreparedStatement" should not be set more than once

           Code Smell
        6. SQL queries should retrieve only necessary fields

           Code Smell
        7. Avoid using "FetchType.EAGER"

           Code Smell
        8. High frame rates should not be used

           Code Smell
        9. Exact alarms should not be abused

           Code Smell
        10. Proper Sensor Resource Management

           Code Smell

        Constant parameters in a "PreparedStatement" should not be set more than once

        intentionality - efficient
        maintainability
        Code Smell
        • sql
        • sustainability

        The java.sql.PreparedStatement represents a precompiled SQL statement that can be efficiently executed multiple times.

        Why is this an issue?

        How can I fix it?

        More Info

        The PreparedStatement is frequently used in loops because it allows to conveniently set parameters. A small optimization is possible by setting constant parameters outside the loop or hard-coding them in the query whenever possible.

        What is the potential impact?

        • Performance: the unnecessary calls to the setter methods bring overhead.
        • Sustainability: the extra overhead has a negative impact on the environment.
          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube Community BuildAnalyze code in your
          on-premise CI
          Available Since
          10.5
        • SonarQube ServerAnalyze code in your
          on-premise CI
          Developer Edition
          Available Since
          10.5

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use