Code Scanning in Cloud Manager | AEM as Cloud Service | Fails | Community
Skip to main content
N
NehaMa
Level 4
June 19, 2026
Question

Code Scanning in Cloud Manager | AEM as Cloud Service | Fails

  • June 19, 2026
  • 2 replies
  • 45 views

Step errors

  • The SonarQube quality scan could not be performed due to an internal connectivity issue. This may be caused by custom configuration. More details may be found in the log. If this recurs, please contact Adobe Support.

We get above error executing the pipeline and in logs it gives

sonar (default-cli) on project racv-aem: Can not execute Findbugs with a timeout threshold value of 1200000 milliseconds: TimeoutException -> [Help 1]

 

Let us know how can we debug it furthur it looks all classes even external dependencies are getting scanned.

 

 

2 replies

ChitraMadan
Community Advisor
ChitraMadanCommunity Advisor
Community Advisor
June 19, 2026

Hi ​@NehaMa ,

Can you please check below:

  • Import-Package for anything available as an OSGi bundle already (most AEM/Adobe/Felix libs).Only use Embed-Dependency for things needed inside your bundle.
  • Anything supplied by the AEM runtime (Sling APIs, JCR APIs, OSGi APIs, AEM uber-jar) should be marked as provided, not compile.

Thanks,

Chitra

    N
    NehaMaAuthor
    Level 4
    June 21, 2026

    thanks ​@ChitraMadan  - cross verified pom and updated considering above , it worked.

      avesh_narang
      avesh_narang
      Level 4
      June 22, 2026

      ​@NehaMa  It seems the failure was due to improper dependency scoping and packaging where AEM runtime libraries were bundled inside the application instead of being referenced via OSGi imports and causing Sonar’s static analysis to time out. Correcting OSGi dependency management as ​@ChitraMadan  mentioned reduced the scan scope and restored pipeline stability.

      Thanks 

       

        Terms & ConditionsAccessibility statement

        Loading footer...