Core AEM, Sling, or Apache Felix bundles restart on stopping and starting custom bundle in the Apache Felix Web Console (/system/console). This issue also happens during code deployments that include the bundle.


The custom bundle is causing the system bundle to restart, as one of the custom bundles exports a java package that is imported by a Felix Framework core bundle.


To debug this issue, follow these steps:

  1. Go to http://aem-host:port/system/console/depfinder, and log in as administrator.

  2. Click Find Duplicate Exports.

  3. Search the page for your custom bundle exporting some library that is used by out of the box AEM, Sling, or Felix bundles.

However, if the above steps do not work, follow these steps:

  1. Go to http://aem-host:port/system/console/bundles UI, and open each of your custom bundles in a new browser tab.

  2. Locate the Importing Bundles section, and see which bundles are importing the exports of your custom bundles.

  3. Find any out-of-the-box (OOTB) bundles that are importing from the exports of your bundles.

  4. Click the importing bundle and see Imported Packages.

  5. The package being imported from your custom bundle is listed.

Based on your findings from the above steps, modify your pom.xml file to avoid exporting core libraries through Export-Package. For information on how to update the <Export-Package> tag, refer the bundle plug-in documentation.

이 작업에는 Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License의 라이센스가 부여되었습니다.  Twitter™ 및 Facebook 게시물은 Creative Commons 약관을 적용받지 않습니다.

법적 고지 사항   |   온라인 개인 정보 보호 정책