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

AEM 6.5 Bundles not installing under {project}/install

  • October 29, 2019
  • 13 replies
  • 13609 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

    U
    Adobe Employee
    user05162Adobe Employee
    Adobe 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
      Level 2
      April 6, 2020
      This worked for me!
      S
      sdouglasmcSonovaAuthor
      Level 4
      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
      A
      Adobe Employee
      aemmarc2Adobe Employee
      Adobe Employee
      October 30, 2019

      RE : We are using snapshot builds.

      S
      sdouglasmcSonovaAuthor
      Level 4
      October 30, 2019

      We use snapshot builds for testing.  But either way, we still are running into the same issue with release versions.  Unless there is something drastically wrong that snapshot builds screw it all up.

      A
      Adobe Employee
      aemmarc2Adobe Employee
      Adobe Employee
      October 30, 2019

      Generally with SNAPSHOT bundles you're not incrementing the build number and newer deploys won't get picked up

      So for example the bundle from the 23rd that was picked up under :

      /apps/yyy/install/yyy-wcms.core-3.11.1-SNAPSHOT.jar

      What's the current build you're trying to deploy today on the 30th? Is it still 3.11.1 ?

      S
      sdouglasmcSonovaAuthor
      Level 4
      October 30, 2019

      It is.  However, I can easily change this.  The odd thing is though, if I uninstall the package and delete it, it still shows up in the osgi-installer.  Is that normal?

      A
      Adobe Employee
      aemmarc2Adobe Employee
      Adobe Employee
      October 30, 2019

      Try incrementing the build number to 3.11.2 and I assure you it will pick up the bundle.

      In regards to the uninstall behavior you're seeing I'd need to see logs.  If this is a concern for you, please raise a Daycare ticket.

      S
      sdouglasmcSonovaAuthor
      Level 4
      October 30, 2019

      While the new 3.11.2 appears in the install folder, the osgi is still pointed to the older version, still saying installed on the 23rd.

      A
      Adobe Employee
      aemmarc2Adobe Employee
      Adobe Employee
      October 30, 2019

      Did you just rename the JAR file, or did you increment the build in the POM files and re-compile?

      S
      sdouglasmcSonovaAuthor
      Level 4
      October 30, 2019

      hahahahha... of course I incremented the build in the POM files and re-compiled.

        Show more replies
        Terms & ConditionsAccessibility statement

        Loading footer...