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
  • 13590 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
    Adobe Employee
    aemmarc2Adobe EmployeeAccepted solution
    Adobe Employee
    October 30, 2019

    Just checking. 

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

      S
      sdouglasmcSonovaAuthor
      Level 4
      October 30, 2019

      It seems to have started to happen when we switched over to an external datastore and shared between author and publish (going the binaryless replication route).  What is also interesting is that the .ser files under launchpad/installer are all from before those dates too.

      puneet_lamba
      puneet_lamba
      Level 2
      June 6, 2020

      I did not see this issue with the 6.5 beta version. However, with archetype13-based projects, the alpha 6.5.4 version of AEM doesn't seem to update a bundle contained within a package if the bundle is already installed. (I didn't try updating the version of the bundle, since I'm just updating the snapshot version in development.) However, using an archetype23-based project against the alpha 6.5.4 version of AEM seems to work fine. 

       

      I determined that with archetype13, the Maven build still generates the correct packages and AEM actually returns a 200 ok message. So, something is going wrong within AEM but I didn't see any related logs being generated and wasn't motivated to debug this since I've moved on to archetype23. 

       

      In cases where I still need to work with an archetype13-based project, I just define an alias for a curl command to directly update the bundle (i.e. not part of a package) in AEM and that works just fine. 

      Terms & ConditionsAccessibility statement

      Loading footer...