AEM 6.4 (adobe-livecycle-jboss.ear) cannot be deploye...

[ccp123456789]

Hi All,

adobe-livecycle-jboss.ear.failed log

We are deploying the AEM6.4 on RHEL with the Jboss 7.0.6.

The package we will deploy:

1) adobe-assembler-ivs.ear

2) adobe-livecycle-cq-author.ear

3) adobe-livecycle-native-jboss-x86_linux.ear

4) adobe-livecycle-output-ivs-jboss.ear

5) adobe-workspace-client.ear

6) adobe-livecycle-jboss.ear

For above .ear we can deploy all EXCEPT the 'adobe-livecycle-jboss.ear'

We open the 'adobe-livecycle-jboss.ear.failed' and found the error message 'org.apache.commons.discovery.discoveryexception: No implementation defined for org.apache.commons.logging.logfactory'.

After we did some research we found that the AEM logging jar file might be conflict with the JBoss jar file. But we have no idea how to fix it.

Please kindly offer your help. Thank you.

[Mayank_Gandhi · Accepted solution]

@ccp123456789 

Looks like a known issue:

https://issues.redhat.com/browse/JBEAP-13646

This issue is coming because of the removal of org.slf4j.jcl-over-slf4j module.

 I guess there a patch or a way around this. Maybe JBoss upgrade or AEM forms patch. Kindly reach out to support for final confirmation.

[ccp123456789]

@Mayank_Gandhi

Thanks for your response.

However, except the JBoss version upgrade is there any other workaround to tackle the issue?  The AEM forms 6.4 just mention about the supported Jboss version is JBoss® Enterprise Application Platform (EAP) 7.0.6. 

Since I found there is a file call 'commons-logging-jboss-logmanager-1.0.0.Final-redhat-1.jar' under the folder '$JBOSS_HOME/modules/system/layers/base/.overlays/layer-base-jboss-eap-7.0.6.CP.org/jboss/logmanager/commons/logging/main', should I replace it with the 'commons-logging-jboss-logmanager-1.0.3.Final-redhat-1.jar' ? 

https://maven.repository.redhat.com/ga/org/jboss/logmanager/commons-logging-jboss-logmanager/1.0.3.F...

[Mayank_Gandhi]

@ccp123456789 We support minor upgrade of App server.

[Mayank_Gandhi]

@ccp123456789 I checked internally this might be fixed in AEMForms-6.4.0-0018. I would recommend not to do manual changes.