Hi Team,
We are facing an issue with Java analysis in SonarQube deployed as a pod on AWS EKS.
Environment
SonarQube Version: 26.4.0.121862 (Community Build)
Deployment: Kubernetes (AWS EKS)
SonarQube runs inside an EKS pod
CI/CD:
AWS CodePipeline
AWS CodeBuild
Scanner Runtime Tested:
Java 17 (Amazon Corretto)
Java 21 (Amazon Corretto)
Maven Scanner Versions Tested:
sonar-maven-plugin 3.11.x / 4.x
sonar-maven-plugin 5.2.x
Project Type: Java (Spring Boot / Maven)
Sample Service Used for Testing: demo-service
Current Behavior
With sonar-maven-plugin 5.2.x
The scan fails during scanner-engine provisioning with SHA/hash mismatch errors.
Example:
Expected hash != Actual hash
Scanner engine provisioning failure
With sonar-maven-plugin 4.x and below
The pipeline completes successfully without errors, but Java analysis does not happen.
Observed warning:
[WARNING] No language plugins are installed.
What Works
Java files are detected and indexed successfully
Around 268 Java files are indexed
Quality profile for Java loads successfully
Active rules load successfully
CPD Block Indexer runs
Analysis report uploads successfully
Background task status shows SUCCESS
What Does Not Work
SonarJava Sensor does not run
No Java LOC/issues are visible in UI
Dashboard shows:
“Main branch has no lines of code”
Important Log Snippet
[INFO] Loading plugins for detected languages
[INFO] Load/download plugins (done) | time=51ms
[WARNING] No language plugins are installed.
[INFO] Sensor Java CPD Block Indexer
It appears the Java plugin is not being loaded during scanner-side analysis runtime.
Plugin Verification
The installed plugins API confirms the Java plugin is present:
key: java
requiredForLanguages: java, jsp
type: BUNDLED
filename: sonar-java-plugin-8.27.0.43088.jar
Plugin locations checked:
/opt/sonarqube/lib/extensions/
Contains:
sonar-java-plugin-8.27.0.43088.jar
/opt/sonarqube/extensions/plugins/
Contains only:
README.txt
We also tested manually copying the plugin into:
/opt/sonarqube/extensions/plugins/
but SonarQube fails to start due to duplicate plugin conflicts.
Additional Validation Performed
We already tested the following:
Java 17 and Java 21 scanner runtimes
sonar-maven-plugin 3.x, 4.x, and 5.x
Clearing ~/.sonar/cache
Multiple fresh project keys
Running with and without sonar-project properties
Verified correct project path and source path
Verified buildspec.yml path handling using:
cd demo-service
Verified pom.xml and src directories are correctly accessible in CodeBuild
Verified Java sources are indexed successfully
Tried scanner execution from different working directories
Network / Connectivity Validation
The SonarQube endpoint is accessed through:
CloudFront
Corporate Zscaler network path
We validated connectivity extensively:
Tested with proxy
Tested without proxy
Tested with NO_PROXY configuration
Tested direct curl downloads
Verified SHA/hash consistency through curl downloads
Connectivity and artifact downloads appear successful outside the scanner runtime.
Deployment Architecture
SonarQube runs as a pod inside AWS EKS
AWS CodePipeline triggers AWS CodeBuild
CodeBuild executes Maven sonar scans
Communication happens through CloudFront ingress endpoint to SonarQube
Our Observation / Doubt
It appears bundled plugins are visible on the server side but are not being loaded into the scanner-side runtime during analysis execution.
Because:
Plugin exists and is reported by API
Java files are indexed
Quality profiles load
But Java sensor never executes
Questions
How are BUNDLED plugins expected to be activated in SonarQube 26.4 Community Build?
Is any additional configuration required for scanner-side language plugin loading?
Is this a known issue with SonarQube 26.4 Community Build and Maven scanner compatibility?
Is there any recommended stable scanner version for Java analysis with SonarQube 26.4?
Please let us know if any additional logs or diagnostics are required.
Plugin file is non-empty:
-r-xr-x—. 1 sonarqube root 20M Apr 8 07:52
/opt/sonarqube/lib/extensions/sonar-java-plugin-8.27.0.43088.jar
Size: 20MB — file is intact.
So the plugin is present and non-empty.
Something in the stack is interfering with JAR delivery to the scanner.
We are running SonarQube on AWS EKS behind CloudFront.
CodeBuild triggers the Maven scan externally.
Could you advise what layer might be blocking
plugin delivery from server to scanner?
Thanks,
Raghu