# SonarCloud analysis fails for PMD reports - Visit of Component X failed

**URL:** <https://community.sonarsource.com/t/sonarcloud-analysis-fails-for-pmd-reports-visit-of-component-x-failed/48238>\
**Category:** SonarQube Cloud\
**Tags:** external\_issues, sonarqube-cloud\
**Created:** [August 17, 2021, 3:23pm UTC](https://community.sonarsource.com/t/sonarcloud-analysis-fails-for-pmd-reports-visit-of-component-x-failed/48238 "2021-08-17T15:23:46Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ivan\_Kozhirug](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ivan_kozhirug/32/24987_2.png) [@Ivan\_Kozhirug](https://community.sonarsource.com/u/Ivan_Kozhirug)\
**Post date:** [August 17, 2021, 3:23pm UTC](https://community.sonarsource.com/t/sonarcloud-analysis-fails-for-pmd-reports-visit-of-component-x-failed/48238/1 "2021-08-17T15:23:46Z")

</div>

- versions used - SonarCloud

- error observed  
`Fail to process issues of component 'EDITED_BECAUSE_OF_COMPANY_POLICY.java:PULL_REQUEST:17' (Visit of Component {key=EDITED_BECAUSE_OF_COMPANY_POLICY.java:PULL_REQUEST:17,type=FILE} failed)`

- steps to reproduce

1. Send a PMD report to SonarCloud. It works OK the first time - all expected Code Smells are reported
2. Commit changes to your code, so SonarCloud tries to analyze the code again. You’ll get the error above

- NOTE  
Noticed that this is exactly the same as the thing discussed in this closed thread: [https://community.sonarsource.com/t/fail-to-process-issues-of-x-visit-of-component-x-failed/44898](https://community.sonarsource.com/t/fail-to-process-issues-of-x-visit-of-component-x-failed/44898)

The bug is listed as fixed - [https://jira.sonarsource.com/browse/SONAR-15091](https://jira.sonarsource.com/browse/SONAR-15091) but obviously not in SonarCloud. So I guess the thing that is described in the bug still happens in SonarCloud:

> If an issue is imported from an external rule engine with an empty message (“”), it will end up being saved in the DB with a null message.  
> The next time the project is analyzed with the same issue, the issue tracking fails with a NullPointerException because of the issue without message in the DB.

---

<div class="post-metadata">

**Author:** ![Claire\_Villard](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/claire_villard/32/27065_2.png) [@Claire\_Villard](https://community.sonarsource.com/u/Claire_Villard)\
**Post date:** [August 31, 2021, 11:58am UTC](https://community.sonarsource.com/t/sonarcloud-analysis-fails-for-pmd-reports-visit-of-component-x-failed/48238/2 "2021-08-31T11:58:09Z")

</div>

Hi @Ivan_Kozhirug, welcome to the community!

Thanks for raising the issue, with all the details. The issue is confirmed, we will work on a fix.

---

<div class="post-metadata">

**Author:** ![Claire\_Villard](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/claire_villard/32/27065_2.png) [@Claire\_Villard](https://community.sonarsource.com/u/Claire_Villard)\
**Post date:** [September 2, 2021, 12:56pm UTC](https://community.sonarsource.com/t/sonarcloud-analysis-fails-for-pmd-reports-visit-of-component-x-failed/48238/3 "2021-09-02T12:56:24Z")

</div>

Hi @Ivan_Kozhirug ,

We deployed a fix for this issue. Could you please re-test and confirm it works fine now?