Sonarqube measures use http get, but parameters too large, and my nginx only close the connectio without any message

Template for a good bug report, formatted with Markdown:

  • versions used (SonarQube, Scanner, Plugin, and any relevant extension)
    Community EditionVersion 7.9.3 (build 33349)
  • error observed (wrap logs/code around triple quote ``` for proper formatting)
  • steps to reproduce
    Choose a project and click “Measures”
  • potential workaround
    Just access sonarqube directly.

P.S.: use the #bug:fault sub-category if you’re hitting a specific crash/error , or the #bug:fp sub-category for rules-related behaviour

url parameters:
metricKeys=new_technical_debt%2Cafferent-couplings%2CXanFindingMetric_All%2Cblocker_violations%2Cbugs%2Cburned_budget%2Cbusiness_value%2Cclasses%2Ccode_smells%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%2Ccritical_severity_vulns%2Ccomplexity%2Cdirectories%2Cduplicated_blocks%2Cnew_duplicated_blocks%2Cduplicated_files%2Cduplicated_lines%2Cduplicated_lines_density%2Cnew_duplicated_lines_density%2Cnew_duplicated_lines%2Cefferent-couplings%2Ceffort_to_reach_maintainability_rating_a%2Cfalse_positive_issues%2Cfiles%2Cfunctions%2Cgenerated_lines%2Cgenerated_ncloc%2Chigh_severity_vulns%2Cinfo_violations%2Cinherited_risk_score%2Cviolations%2Cline_coverage%2Cnew_line_coverage%2Clines%2Cncloc%2Clines_to_cover%2Cnew_lines_to_cover%2Clow_severity_vulns%2Csqale_rating%2Cnew_maintainability_rating%2Cmajor_violations%2Cmedium_severity_vulns%2Cminor_violations%2Cmissing_package_info%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%2CXanFindingMetric_New%2Cnumber-of-classes-and-interfaces%2Cpackage%2Copen_issues%2Cpackage-dependency-cycles%2Cprojects%2Calert_status%2Creliability_rating%2Cnew_reliability_rating%2Creliability_remediation_effort%2Cnew_reliability_remediation_effort%2Creopened_issues%2Crules_compliance_index%2Crules_compliance_rating%2Csecurity_hotspots%2Csecurity_rating%2Cnew_security_rating%2Csecurity_remediation_effort%2Cnew_security_remediation_effort%2Csecurity_review_rating%2Cskipped_tests%2Cstatements%2Cteam_size%2Csqale_index%2Csqale_debt_ratio%2Cnew_sqale_debt_ratio%2Ctotal_dependencies%2Ctotal_vulnerabilities%2Cuncovered_conditions%2Cnew_uncovered_conditions%2Cuncovered_lines%2Cnew_uncovered_lines%2Ctest_execution_time%2Ctest_errors%2Ctest_failures%2Ctests%2Ctest_success_density%2Cvulnerabilities%2Cvulnerable_component_ratio%2Cvulnerable_dependencies%2Cwont_fix_issues%2CXanFindingMetric_Blocker%2CXanFindingMetric_Critical%2CXanFindingMetric_DependencyCheck%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_46%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_55%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_49%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_6%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_48%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_44%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_43%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_47%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_45%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_32%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_31%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_57%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_58%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_59%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_62%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_66%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_56%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_64%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_63%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_11%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_12%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_67%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_68%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_69%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_65%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_60%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_61%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_54%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_53%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_1%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_14%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_5%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_73%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_74%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_75%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_3%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_4%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_78%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_79%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_17%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_20%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_21%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_51%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_50%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_30%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_18%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_19%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_2%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_41%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_23%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_77%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_29%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_39%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_37%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_38%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_40%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_16%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_15%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_42%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_7%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_13%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_8%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_72%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_71%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_70%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_26%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_27%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_24%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_25%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_76%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_34%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_33%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_35%2CXanFindingMetric_XANITIZER_PROBLEM_TYPE_36%2CXanFindingMetric_Info%2CXanFindingMetric_Major%2CXanFindingMetric_Minor%2CXanFindingMetric_SpotBugs

Greetings Team,

It looks like a community-supported plugin for Xanitizer has added a lot of new Measures that have to be queried for. (To be honest, I’m not sure which one, but it appears to be related to Xanitizer :smiley: )

Not much to do other than adjust your Nginx configuration to fit your needs.

1 Like

Thanks for your quick reply. I have tried adjust the nginx, but no luck, so ask it here. It is fine when I use OKhttpclient access the measures url, I found it access by HTTP 1.1, but with chrome, it just close the connection without any message, and no more log on nginx, just see:

testsonar.org [10.17.82.30] - [01/Jul/2020:01:28:29 +0000] "-" 000 0 "-" "-" 4409 0.000 [] - - - -  56e2e119bfc46b41fa87fcf8d9396a59