AEM 6.5 Bundles not installing under {project}/install | Community
Skip to main content
S
sdouglasmcSonova
New Participant
October 29, 2019
Solved

AEM 6.5 Bundles not installing under {project}/install

  • October 29, 2019
  • 13 replies
  • 13589 views

We are upgrading to AEM6.5 from 6.3.  We have set up a shared NFS and everything seems to work fine. 

But since then, AEM doesn't appear to install new bundles of higher versions of our custom projects.  So, for example, {project-b}/install/project-b.jar will not trigger a bundle OSGI install.

I'm not sure the two are related but it does seem a bit odd.  Could something be cached?  Could installing on both author and publish cause issues?  

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

    Just checking. 

    Feel free to log a Daycare ticket to troubleshoot this further.

    13 replies

    Show previous replies
    A
    aemmarc2
    Employee
    October 30, 2019

    RE : We are using snapshot builds.

    S
    sdouglasmcSonovaAuthor
    New Participant
    October 30, 2019

    We are using snapshot builds.  It does look like it is being mapped to the one installed on the 23rd.  I tried the above steps but nothing changed.  Package installs with latest front end changes but the install folder doesn't seem to get picked up anymore.  I don't see anything in the logs either.

    com.xxx.yyy.wcms.core1571846896324/200jcrinstall:/apps/yyy/install/yyy-wcms.core-3.11.1-SNAPSHOT.jar (3.11.1.SNAPSHOT)INSTALLED
    18:53:38:067 2019-Oct-23
    U
    user05162
    Employee
    October 30, 2019

    After installing the latest version of the bundle, Go to [1] and check if the bundle is still mapped to the older jar file.

    If yes, there might be something wrong with the OSGI installer. You can follow the steps below:

    - Stop the AEM instance

    - Go to <AEM_Installation_Directory>crx-quickstart directory

    - Rename the launchpad to launchpad_bkp

    - Start the instance and this should create a new launchpad folder. Wait for the instance to startup

    - Stop the instance and delete the newly created launchpad folder

    - Restore launchpad_bkp to launchpad

    - Start the instance

    [1] http://<host>:<port>/system/console/osgi-installer

      Y
      ykadaru-konrad
      New Participant
      April 6, 2020
      This worked for me!
      Terms & ConditionsAccessibility statement

      Loading footer...