Hello,
I'm trying to remediate security vulnerabilities in our AEM installation. I have downloaded the adobe-aem-forms-jee-hotfix-6.5.23.0-win-jboss.zip file, and extracted it, and I'm running the aemforms65_cfp_install.exe file in the Disk1/InstData/VM folder. The patch kicks off, executes, and succeeds. I then run configuration manager. The first issue I faced was that I had to copy the commons-io-2.5.jar file from the \Adobe_Experience_Manager_Forms\sdk\client-libs\thirdparty folder to the configuration manager lib directory. That got me past my first issue, which was: java.lang.NoClassDefFoundError: org/apache/commons/io/FileUtils. Now that I've moved past that, I'm getting this error:
[2025-07-15 11:11:24,100], SEVERE, Thread-6, com.adobe.livecycle.lcm.feature.configureLC.MergeEarsTask, Task failed
com.adobe.livecycle.lcm.core.LCMException[ALC-LCM-010-200]: Failed to merge Ears.
at com.adobe.livecycle.lcm.feature.configureLC.MergeEars.mergeEars(MergeEars.java:221)
at com.adobe.livecycle.lcm.feature.configureLC.MergeEars.mergeEars(MergeEars.java:151)
at com.adobe.livecycle.lcm.feature.configureLC.MergeEars.mergeAllEars(MergeEars.java:94)
at com.adobe.livecycle.lcm.feature.configureLC.MergeEarsTask$ActualTask.<init>(MergeEarsTask.java:74)
at com.adobe.livecycle.lcm.feature.configureLC.MergeEarsTask$1.construct(MergeEarsTask.java:52)
at com.adobe.livecycle.lcm.core.tasks.SwingWorker$2.run(SwingWorker.java:114)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.NoClassDefFoundError: org/apache/xpath/XPathAPI
at com.adobe.livecycle.lcm.feature.configureLC.MergeEars2.mergeAppXML(MergeEars2.java:778)
at com.adobe.livecycle.lcm.feature.configureLC.MergeEars2.mergeEar(MergeEars2.java:280)
at com.adobe.livecycle.lcm.feature.configureLC.MergeEars2.mergeEars(MergeEars2.java:228)
at com.adobe.livecycle.lcm.feature.configureLC.MergeEars.mergeEars(MergeEars.java:210)
... 6 more
Caused by: java.lang.ClassNotFoundException: org.apache.xpath.XPathAPI
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
... 10 more
xalan-2.7.2.jar is present in the Adobe\Adobe_Experience_Manager_Forms\configurationManager\lib directory, and I confirmed that this jar contains org.apache.xpath.XPathAPI.class. I was unable to find anyone else having this specific classloader issue. Any advice will be appreciated.
Thanks!
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @RyanK99,
This is a prevalent issue while installing the patch for AEM Forms JEE patch. The same steps have also been documented in the Patch installation guide[0]. You will need to refer to section "4. Install AEM Forms on JEE service pack:" to avoid seeing this issue in the future.
"
Before running Configuration Manager using ConfigurationManager.exe or ConfigurationManager_IPv6.exe, navigate to <AEMForms_Install_Dir>\configurationManager\bin
directory and replace the ConfigurationManager.lax and ConfigurationManager_IPV6.lax with the latest ConfigurationManager.lax and ConfigurationManager_IPV6.lax files, Search, and replace axis-1.4.1.1.jar with axis-1.4.1.2.jar in these two files."
Pranay
Views
Replies
Total Likes
I did manage to find a solution for this. It turns out that the configuration manager I was running was specifically looking for 2 jars that were not present in the lib directory. Those were xalan-2.7.1.jar and serializer-2.7.1.jar. Once these were added, the installer got past the ear merge step and I was able to deploy the ears to JBoss (wildfly). Unfortunately, the last step to verify the server is up is unable to locate some axis related soap classes (SoapConstants), but I have no idea which axis jar file it is expecting. I tried throwing all the axis jars available into the lib directory, but none seemed to get picked up by CFM, but I know the server is up now. If anyone knows which axis jar to try, that might be good to know, but otherwise, I think we're good. Thanks!
Views
Replies
Total Likes
Hi @RyanK99,
This is a prevalent issue while installing the patch for AEM Forms JEE patch. The same steps have also been documented in the Patch installation guide[0]. You will need to refer to section "4. Install AEM Forms on JEE service pack:" to avoid seeing this issue in the future.
"
Before running Configuration Manager using ConfigurationManager.exe or ConfigurationManager_IPv6.exe, navigate to <AEMForms_Install_Dir>\configurationManager\bin
directory and replace the ConfigurationManager.lax and ConfigurationManager_IPV6.lax with the latest ConfigurationManager.lax and ConfigurationManager_IPV6.lax files, Search, and replace axis-1.4.1.1.jar with axis-1.4.1.2.jar in these two files."
Pranay
Views
Replies
Total Likes
Views
Likes
Replies