Expand my Community achievements bar.

SOLVED

AEM Forms 6.5.18 installation on Linux fails to deploy ear files

Avatar

Level 3

hi all,

 

I'm currently installing the latest AEM Forms 6.5.18 on a RHEL server ("Experience Manager 6.5.18.0 Forms installer for JBoss EAP and Linux").

I already installed java 11.0.21 and made it available in bash and set the JAVA_HOME environment variable.

 

I successfully ran the install.bin script after unpacking the installer zip file.

We had to add a JAVA_TOOL_OPTIONS environment variable in order to run the install.bin

export JAVA_TOOL_OPTIONS=-Djdk.util.zip.disableZip64ExtraFieldValidation=true

 

After the successful installation, I unzipped the jboss from the third_party folder.

JBoss can startup completly using the bin/standalone.sh

 

The next step is to create the ear files for adobe livecycle, I use the ConfigurationManagerCLI.sh to do this.

/ConfigurationManagerCLI.sh configureLiveCycle -f cli_aemforms_config.txt

I exclude all solutioncomponents except for ALC-LFS-Output.

This generates 3 ear files: 

  • adobe-livecycle-jboss.ear
  • adobe-livecycle-native-jboss-x86_linux.ear
  • adobe-output-ivs-jboss.ear

I copy those files to the jboss/standalone/deployments directory and start jboss.

But this results in multiple error messages.

 

The adobe-livecycle-native-jboss-x86_linux.ear produces the following error:

Caused by: java.lang.ClassNotFoundException: javax.management.j2ee.statistics.Stats from [Module "deployment.adobe-livecycle-native-jboss-x86_linux.ear.CommonNatives.war" from Service Module Loader]
	at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:255)
	at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410)
	at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398)
	at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116)
	... 32 more

The ear file is missing a dependency.

I can resolve this error by manually unzipping the ear file and including the javax.management.j2ee.api dependency in META-INF/jboss-deployment-structure.xml

 

The other ear file: 

  • adobe-livecycle-jboss.ear

Throws errors that dependencies are missing

14:50:48,592 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 42) WFLYSRV0010: Deployed "adobe-livecycle-jboss.ear" (runtime-name : "adobe-livecycle-jboss.ear")
14:50:48,600 INFO  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
WFLYCTL0184:    New missing/unsatisfied dependencies:
      service jboss.deployment.subunit."adobe-livecycle-jboss.ear"."AACComponent.jar".beanmanager (missing) dependents: [service jboss.deployment.subunit."adobe-livecycle-jboss.ear"."AACComponent.jar".weld.weldClassIntrospector, service jboss.deployment.subunit."adobe-livecycle-jboss.ear"."AACComponent.jar".batch.artifact.factory]
      service jboss.deployment.subunit."adobe-livecycle-jboss.ear"."AACComponent.jar".deploymentCompleteService (missing) dependents: [service jboss.deployment.subunit."adobe-livecycle-jboss.ear"."TrustStoreComponent.jar".INSTALL, service jboss.deployment.unit."adobe-livecycle-jboss.ear".deploymentCompleteService]
      service jboss.deployment.subunit."adobe-livecycle-jboss.ear"."AACComponent.war".beanmanager (missing) dependents: [service jboss.deployment.subunit."adobe-livecycle-jboss.ear"."AACComponent.war".batch.artifact.factory]
      service jboss.deployment.subunit."adobe-livecycle-jboss.ear"."AACComponent.war".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."adobe-livecycle-jboss.ear".deploymentCompleteService, service jboss.deployment.subunit."adobe-livecycle-jboss.ear"."TrustStoreComponent.war".INSTALL]
      service jboss.deployment.subunit."adobe-livecycle-jboss.ear"."CoreSystemConfigComponent.jar".beanmanager (missing) dependents: [service jboss.deployment.subunit."adobe-livecycle-jboss.ear"."CoreSystemConfigComponent.jar".batch.artifact.factory, service jboss.deployment.subunit."adobe-livecycle-jboss.ear"."CoreSystemConfigComponent.jar".weld.weldClassIntrospector]
      service jboss.deployment.subunit."adobe-livecycle-jboss.ear"."CoreSystemConfigComponent.jar".deploymentCompleteService (missing) dependents: [service jboss.deployment.unit."adobe-livecycle-jboss.ear".deploymentCompleteService, service jboss.deployment.subunit."adobe-livecycle-jboss.ear"."adobe-wkf-admin.jar".INSTALL]
      service jboss.deployment.subunit."adobe-livecycle-jboss.ear"."CoreSystemConfigComponent.war".beanmanager (missing) dependents: [service jboss.deployment.subunit."adobe-livecycle-jboss.ear"."CoreSystemConfigComponent.war".batch.artifact.factory]
      service jboss.deployment.subunit."adobe-livecycle-jboss.ear"."CoreSystemConfigComponent.war".deploymentCompleteService (missing) dependents: [service jboss.deployment.subunit."adobe-livecycle-jboss.ear"."adobe-docmanager-init.war".INSTALL, service jboss.deployment.unit."adobe-livecycle-jboss.ear".deploymentCompleteService]

 

Do I need to deploy additional files or libraries and where can I find those?

 

Thank you!

Topics

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

1 Accepted Solution

Avatar

Correct answer by
Level 3

The issue with the server installation has been resolved!

 

The underlying issue was that the MySQL server was not setup and that the JBoss was not started with the -c lc_mysql.xml parameter.

Thus resulting in the strange errors mentioned in my stacktrace.

 

Creating the database and correcting the lc_mysql.xml configuration file resolves the issue.

 

 

View solution in original post

9 Replies

Avatar

Employee Advisor

@StevenRymenans 

Quick checks: 

- AEM Forms on JEE support Oracle JDK 11 (64 bit) for application server JBoss EAP 7.4 only so ensure you have the correct versions.

- What is the Linux installation OS version? Did you install all the required RPMs- https://experienceleague.adobe.com/docs/experience-manager-learn/forms/adaptive-forms/installing-aem... 

Please share the complete log file for a review, if the issue persists.

Avatar

Level 3

Hi,

 

The JDK is the Oracle JDK 11 (64 bit) and the RPMs are all installed.

I regenerated the EAR files and started the jboss server, sadly this doesn't resolve the issue.

I attached the server.log.

 

 

 

Avatar

Employee Advisor

@StevenRymenans 

Since you have selected just the output service so the other undeployed services that have excerpts in the JBoss EAR are causing the problem[0]. You can comment out unnecessary services in the META-INF/jboss-service.xml descriptor file of the EAR.

Haven't tried this option using CLI mode as we get to enable/disable the modules in the GUI.

[0] - 

2023-11-27 08:35:57,778 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "adobe-livecycle-jboss.ear")]) - failure description: {
    "WFLYCTL0412: Required services that are not installed:" => [
        "jboss.naming.context.java.comp.adobe-livecycle-jboss.\"TrustStoreComponent.jar\".AdobeIDP2UI_TrustStoreComponent",
        "jboss.naming.context.java.comp.adobe-livecycle-jboss.\"um.jar\".HibernateSynchronizationDao",
        "jboss.deployment.subunit.\"adobe-livecycle-jboss.ear\".\"um-startup.war\".deploymentCompleteService",
        "jboss.deployment.subunit.\"adobe-livecycle-jboss.ear\".\"adobe-forms-cacheService.war\".beanmanager",
        "jboss.naming.context.java.comp.adobe-livecycle-jboss.adobe-wkf.adobe_TemplateManagerRemoteEJB",
        "jboss.deployment.subunit.\"adobe-livecycle-jboss.ear\".\"adobe-output-config-ejb.jar\".beanmanager",
        "jboss.deployment.subunit.\"adobe-livecycle-jboss.ear\".\"adobe-dsc-bootstrap-ejb.jar\".deploymentCompleteService",
        "jboss.deployment.subunit.\"adobe-livecycle-jboss.ear\".\"AACComponent.war\".beanmanager",
        "jboss.deployment.subunit.\"adobe-livecycle-jboss.ear\".\"adobe-wkf-admin.jar\".deploymentCompleteService",
        "jboss.naming.context.java.comp.adobe-livecycle-jboss.\"um.jar\".LocalUserManagerBean",
        "jboss.naming.context.java.comp.adobe-livecycle-jboss.adobe-wkf.adobe_ProcessManagerRemoteEJB",
        "jboss.deployment.subunit.\"adobe-livecycle-jboss.ear\".\"um-adminui.jar\".beanmanager",
        "jboss.deployment.subunit.\"adobe-livecycle-jboss.ear\".\"adobe-dscf.jar\".beanmanager",

 

Avatar

Level 3

Hi,

 

I tried to remove the excludedSolutions list and just use all the solutions, rebuild the ear file and redeploy it.

But I still got the same kind of errors.

 

Is there anything that I might be missing?

 

 

Avatar

Employee Advisor

@StevenRymenans 

What is the value of entropy on the linux server? Please ensure that the value of entropy >3400 on the server.

If the issue is not resolved after updating the entropy, please raise a support ticket with the EAR file from the server for a review.

Avatar

Level 3

@Pulkit_Jain_ 

 

The entropy value is 1858 (output of 'cat /proc/sys/kernel/random/entropy_avail')

How do I change this on a AWS virtual machine?

 

I already created a support ticket and provided multiple updates, but I haven't receive a single response.

 

I also compared the jboss with the packed jboss of older install files and noticed that the com.adobe.livecycle jboss modules are not under modules/system/layers/base, they are located under modules. 

It seems as if the pre-configured jboss included in the installation is not entirely pre-configured.

 

Avatar

Administrator

@StevenRymenans Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.



Kautuk Sahni

Avatar

Level 3

@kautuk_sahni We opened a ticket with Adobe Support, the installation files don't work for us, we were able to reproduce the issue on a different server. I will update the ticket when Adobe Support has provided a solution.

 

Avatar

Correct answer by
Level 3

The issue with the server installation has been resolved!

 

The underlying issue was that the MySQL server was not setup and that the JBoss was not started with the -c lc_mysql.xml parameter.

Thus resulting in the strange errors mentioned in my stacktrace.

 

Creating the database and correcting the lc_mysql.xml configuration file resolves the issue.