404 on measures tab

SonarQube Server / Community Build
1

Template for a good bug report, formatted with Markdown:

  • SonarQube 8.3.1 build 34397 Enterprise edition
  • 404 on measures api
  • Open measures page on any project
  • No work arounds exist
2

Hello, could you elaborate a bit please?

3

Sorry, was uploading a screen shot.

Happening against URL:
https://XXXXXX/api/measures/component?additionalFields=period&component=ApiTeam_OracleDatabase_Accounting&metricKeys=SMELL_COUNT_ABBREVIATIONS_USAGE%2Cnew_technical_debt%2CSMELL_COUNT_ANTI_PATTERN%2CSMELL_COUNT_BAD_DESIGN%2CSMELL_COUNT_BAD_FRAMEWORK_USAGE%2CSMELL_COUNT_BAD_LOGGING%2Cblocker_violations%2Cbugs%2Cburned_budget%2Cbusiness_value%2Cclasses%2Ccode_smells%2CSMELL_DEBT%2Ccognitive_complexity%2Ccomment_lines%2Ccomment_lines_density%2Cbranch_coverage%2Cnew_branch_coverage%2Cconditions_to_cover%2Cnew_conditions_to_cover%2Cconfirmed_issues%2Ccoverage%2Cnew_coverage%2Ccritical_violations%2Ccomplexity%2Cdirectories%2Cduplicated_blocks%2Cnew_duplicated_blocks%2Cduplicated_files%2Cduplicated_lines%2Cduplicated_lines_density%2Cnew_duplicated_lines_density%2Cnew_duplicated_lines%2Ceffort_to_reach_maintainability_rating_a%2Cfalse_positive_issues%2Cfiles%2Cfunctions%2Cgenerated_lines%2Cgenerated_ncloc%2CSMELL_COUNT_HOW_COMMENT%2CSMELL_COUNT_INDECENT_EXPOSURE%2Cinfo_violations%2Cviolations%2Cline_coverage%2Cnew_line_coverage%2Clines%2Cncloc%2Clines_to_cover%2Cnew_lines_to_cover%2Csqale_rating%2Cnew_maintainability_rating%2Cmajor_violations%2CSMELL_COUNT_MEANINGLESS_COMMENT%2CSMELL_COUNT_MIDDLE_MAN%2Cminor_violations%2CSMELL_COUNT_MISSING_DOCUMENTATION%2CSMELL_COUNT_MISSING_IMPLEMENTATION%2CSMELL_COUNT_MISSING_TEST%2CSMELL_COUNT_MULTIPLE_RESPONSIBILITIES%2Cnew_blocker_violations%2Cnew_bugs%2Cnew_code_smells%2Cnew_critical_violations%2Cnew_info_violations%2Cnew_violations%2Cnew_lines%2Cnew_major_violations%2Cnew_minor_violations%2Cnew_security_hotspots%2Cnew_vulnerabilities%2CSMELL_COUNT_NON_COMPLIANCE_WITH_STANDARDS%2CSMELL_COUNT_NON_EXCEPTION%2CSMELL_COUNT_ODDBALL_SOLUTION%2Copen_issues%2CSMELL_COUNT_OVERCOMPLICATED_ALGORITHM%2CSMELL_COUNT_PRIMITIVES_OBSESSION%2Cprojects%2Calert_status%2CSMELL_COUNT_REFUSED_BEQUEST%2CSMELL_COUNT_REINVENTED_WHEEL%2Creleasability_rating%2Creliability_rating%2Cnew_reliability_rating%2Creliability_remediation_effort%2Cnew_reliability_remediation_effort%2Creopened_issues%2Csecurity_hotspots%2Csecurity_hotspots_reviewed%2Cnew_security_hotspots_reviewed%2Csecurity_rating%2Cnew_security_rating%2Csecurity_remediation_effort%2Cnew_security_remediation_effort%2Csecurity_review_rating%2Cnew_security_review_rating%2Cskipped_tests%2CSMELL_COUNT%2CSMELL_COUNT_SOLUTION_SPRAWL%2CSMELL_COUNT_SPECULATIVE_GENERALITY%2Cstatements%2Cteam_size%2Csqale_index%2Csqale_debt_ratio%2Cnew_sqale_debt_ratio%2CSMELL_COUNT_OTHER%2CSMELL_COUNT_UNCOMMUNICATIVE_NAME%2Cuncovered_conditions%2Cnew_uncovered_conditions%2Cuncovered_lines%2Cnew_uncovered_lines%2Ctest_execution_time%2Ctest_errors%2Ctest_failures%2Ctest_success_density%2Ctests%2CSMELL_COUNT_USELESS_TEST%2Cvulnerabilities%2Cwont_fix_issues%2CSMELL_COUNT_WRONG_LANGUAGE%2CSMELL_COUNT_WRONG_LOGIC

4

BUMP
Re-adding the image as it has expired in the original request.

To give further context, I have no idea what this tab does. I have simply installed the enterprise software, scanned a project and then when I go into the project and click on the measures tab within the application, I was presented an error dialog(see screen shot) and it gave me an error because the resource it tried to access on the server is non existent. I have been asked if its because its doing something when it accesses that page, but I really have no idea whats supposed to be on this page so don’t know what its doing. It almost looks like the installation failed to install a resource.

5

Anything at all on this?

6

Disappointing to see we’re not getting much support here

7

I solved this problem by increasing the max querystring length by editing the web.config file in wwwroot to include the following

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
  <system.web>
    <customErrors mode="Off"/>
    <httpRuntime maxQueryStringLength = "10000" />
  </system.web>
  <system.webServer>
    <security>
      <requestFiltering>
        <requestLimits maxQueryString="10000" />
      </requestFiltering>
    </security>
  </system.webServer>
</configuration>
1 Like
8

I had the same issue and increasing max query string length resolve it. Thanks for posting.

9

I’ve made this update on my web server, but it seems to have no effect. Application logs still report this error.

I’ve made the change in the web.config in the physical path where the sonar server runs from.

restarted IIS and sonar service, to no avail.

10

This worked for me! Thanks so much!
I am on Developer edition with Sonarqube version of 2025.1.0.102418.
Deployed on Azure as a Webapp