Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

Bundle installation and mapping issue in AEM 6.5

Avatar

Level 2

Hi Team,

 

After installing a new package, osgi bundle is not getting reflected under bundles. When we checked in osgi-installer (<ip>:<port>/system/console/osgi-installer), it is showing mapping with old version's bundle here.

We uninstalled and deleted all versions of the the project package from package manager. Now Project is not present in /apps as but when we checked the mapping in osgi-installer and it was still there. 

Installing package after increasing version is installing the bundle.

 

Manual installation of bundle through Felix console is working fine.

 

Any suggestion on this issue?

Topics

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

6.5
1 Accepted Solution

Avatar

Correct answer by
Level 2

I found the solution for this problem:

 

Issue #1 : Bundle with new version was not getting installed:

The issue was related to an older version of "org.apache.sling.installer.factory.configuration". I installed the newer version of this bundle from <host>:<port>/system/console using the "Install/Update" option at the top right and restarted the instance.

Old version was 1.2.1 and now i have installed 1.3.4.

 

Issue #2: Old bundle was present and if we were deleting it, it was getting reflected after server restart

We checked the bundle in crx-quickstart/launchpad/felix and it was pointing to non existing jar file. So we have deleted this bundle after taking the backup of AEM.

After server restart, bundle was gone from the server.

View solution in original post

8 Replies

Avatar

Community Advisor

Hi @vibhuranjan21,

 

Bundle installation can be done in the below ways:

  1. Via Maven build 
  2. Manually installing it in Felix console
  3. Adding it in the crx-quickstart/install

In general, installing it via maven build is a suggested approach. 

 

As per your query, it seems to be an issue with the version number of your project. Update it and try to install it again.

 

Hope this helps.

 

Thanks,

Kiran Vedantam

Avatar

Level 2

Hi Kiran, I have changed the version multiple times. I have tried with snapshot and release versions both, but nothing is working here.

Avatar

Community Advisor
Once installation is done, are you getting any error in the maven build? Check the maven logs. Also check the error.log for any traces of the issue

Avatar

Level 2
Maven build is fine and there is no error in error.log after installation of the package.

Avatar

Community Advisor

@vibhuranjan21 

Extract your package.zip like how you extract normal zip file and check your bundle version inside the package under jcr_root/apps/<project>-packages/application/install/xxxx.jar and see if it is latest or not.

@Anudeep_Garnepudi There is latest jar present at this path. After installation, same jar is present inside /apps/<project>/install folder as well..

Avatar

Correct answer by
Level 2

I found the solution for this problem:

 

Issue #1 : Bundle with new version was not getting installed:

The issue was related to an older version of "org.apache.sling.installer.factory.configuration". I installed the newer version of this bundle from <host>:<port>/system/console using the "Install/Update" option at the top right and restarted the instance.

Old version was 1.2.1 and now i have installed 1.3.4.

 

Issue #2: Old bundle was present and if we were deleting it, it was getting reflected after server restart

We checked the bundle in crx-quickstart/launchpad/felix and it was pointing to non existing jar file. So we have deleted this bundle after taking the backup of AEM.

After server restart, bundle was gone from the server.

Avatar

Administrator
Thank you for sharing the answer with the community, this would help in posterity.


Kautuk Sahni