Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.

Code Scanning failing in Cloud Manger

Avatar

Level 1

Hi All,

 

I am using AEMaaCS and trying to push custom Lucene index changes to Clod Manager. I am getting build success and failing on "Code scanning" step. Please find the below exception in log:

 

21:27:53,865 [main] [DEBUG] 21:27:53.865 Could not complete symbolic execution:
org.sonar.java.se.ExplodedGraphWalker$MaximumStepsReachedException: reached limit of 16000 steps for method updatettachments#510 in class BVCodeCasesService

 

If I remove custom Lucene index changes, I am getting build success without any issues.

 

filevault-package-maven-plugin:
<artifactId>filevault-package-maven-plugin</artifactId>
<version>1.1.6</version>

 

I am getting local build success and indexes are created in local without any issues.

 

Could you please help me to resolve the issue.

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

8 Replies

Avatar

Community Advisor

The log which you posted seems to be a debug log and probably not relevant for code scanning failure. 
Please check if you have followed these guidelines while namng your indexes https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/operations/index... 

Avatar

Administrator

@RR_MR 

Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!



Kautuk Sahni

Avatar

Level 1

Hi kautuk_sahni,

 

Not yet get any solution for this and trying with all possibilities. I have tried with filevault-package-maven-plugin version with 1.3.0 and getting local build success and failing at Cloud Manager build

 

Error

The index /oak:index/lucene-custom-1 is a customization of the out of the box index /oak:index/lucene which requires a config.xml file under the child node named tika

 

filevault-package-maven-plugin in parent pom file

<plugin>
<groupId>org.apache.jackrabbit</groupId>
<artifactId>filevault-package-maven-plugin</artifactId>
<extensions>true</extensions>
<version>1.3.0</version>
<configuration>
<packageType>application</packageType>
<allowIndexDefinitions>true</allowIndexDefinitions>
<validatorsSettings>
<jackrabbit-packagetype>
<options>
<immutableRootNodeNames>apps,libs,oak:index</immutableRootNodeNames>
</options>
</jackrabbit-packagetype>
<jackrabbit-nodetypes>
<options>
<!-- use the nodetypes and namespaces from the aem-nodetypes.jar
provided in the plugin dependencies -->
<cnds>tccl:aem.cnd</cnds>
</options>
</jackrabbit-nodetypes>
</validatorsSettings>
<properties>
<noIntermediateSaves>true</noIntermediateSaves>
</properties>
</configuration>

Custom Index code 

<?xml version="1.0" encoding="UTF-8"?>
<jcr:root xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:nt="http://www.jcp.org/jcr/nt/1.0" xmlns:oak="http://jackrabbit.apache.org/oak/ns/1.0" xmlns:rep="internal"
jcr:mixinTypes="[rep:AccessControllable]"
jcr:primaryType="nt:unstructured">
<lucene-1-custom-2
jcr:primaryType="oak:QueryIndexDefinition"
async="[async]"
compatVersion="{Long}2"
deprecated="{Boolean}true"
evaluatePathRestrictions="{Boolean}true"
includedPaths="[/content/dam/images/carrier/en]"
queryPaths="[/content/dam/images/carrier/en]"
maxFieldLength="{Long}100000"
reindex="{Boolean}false"
reindexCount="{Long}6"
seed="{Long}-2257980824417909955"
type="lucene">
<facets
jcr:primaryType="nt:unstructured"
secure="statistical"
topChildren="100"/>
<indexRules jcr:primaryType="nt:unstructured">
<nt:unstructured
jcr:primaryType="nt:unstructured"
indexNodeName="{Boolean}true">
<properties jcr:primaryType="nt:unstructured">
<dcTitle
jcr:primaryType="nt:unstructured"
boost="{Double}2.0"
name="jcr:content/metadata/dc:title"
nodeScopeIndex="{Boolean}true"
ordered="{Boolean}true"
propertyIndex="{Boolean}true"
useInSpellcheck="{Boolean}true"
useInSuggest="{Boolean}true"/>
</properties>
</nt:unstructured>
</indexRules>
<tika jcr:primaryType="nt:unstructured">
<config.xml/>
</tika>
</lucene-1-custom-2>
</jcr:root>

 

tika - config.xml

<properties>
<detectors>
<detector class="org.apache.tika.detect.TypeDetector"/>
</detectors>
<parsers>
<parser class="org.apache.tika.parser.DefaultParser">
<mime>text/plain</mime>
</parser>
</parsers>
<service-loader initializableProblemHandler="ignore" dynamic="true"/>
</properties>

config.xml available in tika folder but still deployment is failing at Cloud Manager.

 

Could you please check and suggest any other configurations required.

Avatar

Community Advisor

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/operations/remov...
This could be the possible reason why it is not allowing on AEMaaCS. I checked on our cloud instance and couldn't find oak:index/lucene as well on it.

Avatar

Level 1

Hi Mukesh,

Thanks for the reply.

 

Yes, I have tried with tika config update and successfully deploy custom index to Clod Manager.

When I try to remove custom index, it's update index type property with disabled value and not removing from Crx/de

 

RR_MR_0-1724246890796.png

Could you please help me how to change this type property