Level 2

Solved

RabbitMQ 5.6 and above conflict with AEM 6.5.21 version jar packages

8 replies
1601 views
Translate All

RabbitMQ 5.6 and AEM 6.5.21 versions, my project starts normally and the editing page is working properly

I changed RabbitMQ 5.22 and AEM 6.5.21 versions, the project started normally, but the editing page was blank

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

TethichAccepted solution

Community Advisor

Can you specify the version? Greater than 5.18.0 . Also check if rabbit cannot be resolved in the project bundle.

I already shared which version I used. It is 5.23.0.
Ad for bundle, it says nothing about not being resolved:

Tethich

Community Advisor

Hi @guodongha

Can you go in system console and check your bundles to see if all are running properly ? All dependencies should show as resolved.
Go here:

And for example here is an example of a bundle of mine that has issues:

Also try to check browser console for any errors, even if I doubt you find anything there because to me it seams a backend thing, but still, worth checking.

Translate

G

guodonghaAuthor

Level 2

I have installed what you mentioned and viewed the project screenshot below

This effect should be caused by package conflicts that cannot be resolved. I have excluded the following packages, but the problem has not been resolved and I need help

Translate

Tethich

Community Advisor

Try to lookup online resources on how to include third party dependencies:
https://myaemlearnings.blogspot.com/2021/08/embedding-third-party-dependencyosgi.html
https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-to-use-third-party-api-in-aem/td-p/553767
https://experienceleague.adobe.com/en/docs/experience-manager-learn/forms/creating-your-first-osgi-bundle/include-third-party-jars
https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/including-third-party-bundles-in-aem/m-p/610994

You can always manually covert RabbitMQ jar into a bundle and install it into AEM via the system console. But I guess this is not desirable long term solution. But it can be a temporary solution just to unlock you and be able to move forward with your implementation tasks:
https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-17475
https://medium.com/@manumathew28.94/aem-convert-a-jar-to-an-osgi-bundle-742a51a90327
https://experienceleague.adobe.com/en/docs/experience-cloud-kcs/kbarticles/ka-17475

Translate

kautuk_sahni

Adobe Employee

@guodongha Did you find the suggestion 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!

Translate

Kautuk Sahni

Sign up

Login with SSO

Login to the community

Login with SSO