Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

AEM 6.4 (adobe-livecycle-jboss.ear) cannot be deployed to JBoss EAP 7.0.6

Avatar

Avatar
Validate 1
Level 1
ccp123456789
Level 1

Likes

0 likes

Total Posts

14 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile

Avatar
Validate 1
Level 1
ccp123456789
Level 1

Likes

0 likes

Total Posts

14 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
View profile
ccp123456789
Level 1

24-08-2020

Hi All,

adobe-livecycle-jboss.ear.failed logadobe-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.

 

AEM 6.4

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 1
Level 10
Mayank_Gandhi
Level 10

Likes

278 likes

Total Posts

1,101 posts

Correct Reply

181 solutions
Top badges earned
Validate 1
Contributor 2
Ignite 5
Ignite 3
Ignite 10
View profile

Avatar
Validate 1
Level 10
Mayank_Gandhi
Level 10

Likes

278 likes

Total Posts

1,101 posts

Correct Reply

181 solutions
Top badges earned
Validate 1
Contributor 2
Ignite 5
Ignite 3
Ignite 10
View profile
Mayank_Gandhi
Level 10

24-08-2020

@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.

 

Answers (0)