Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

OSGi Bundle startup issue

GaneshM
Level 4
Level 4

Hi All,

      Recently I'm facing bundle issue on Author environment,  I'm using bamboo job to deploy the package.

The issue is after the deployment, the latest bundles are not installed, the bundles are referring to old bundles whereas the package manager shows as installed state and Publisher work fine. I couldn't find any strange thing in author logs. 

Whenever i restart the author instance, the latest bundles are showing up in system console. 

any pointer would be great help to address this issue.

Thanks in advance.

1 Accepted Solution
GaneshM
Correct answer by
Level 4
Level 4

thanks, everyone. its The JCR Installer Pause Issue

Manualy I've deleted folder under /system/sling/installer/jcr/pauseInstallation. Its working fine. 

 

More info: https://issues.apache.org/jira/browse/SLING-5421 

View solution in original post

0 Replies
smacdonald2008
Level 10
Level 10

Try install your bundle on a fresh AEM machine using Package Manager to see if the real issue is the environment, the way you deploy (bamboo ?? - never heard of using that to deploy a package) or the package. 

GaneshM
Level 4
Level 4

Hi Scott,

     Thanks for checking issue, the same package working fine in Publisher in a vanilla instance.  We are facing this issue, since the last sprint. If its dependency issue, the publisher would have face same issue but it works fine.  

Use case, my last core bundle's build id 100 and I'm deploying the new package with #101, I can see latest package installed state without any error whereas I see bundle build id 100 in system console. After a restart, its works fine.

Wondering what went wrong, heard any similar issue before? any pointers?

 

Thanks Again!

sandeepm744005
Level 5
Level 5

Same issue we also faced it sometime back and root cause was, previous build bundle jar was locked with "root" user.

Go to this path - crx-quickstart\repository\segmentstore and see if your bundle is locked with "Root" or different user ? if yes, then you need to change the permissions using chown command if you are on Linux. 

In our case, someone started the AEM server with root permission and we had to manually update all the files which got locked with "root" user.

GaneshM
Correct answer by
Level 4
Level 4

thanks, everyone. its The JCR Installer Pause Issue

Manualy I've deleted folder under /system/sling/installer/jcr/pauseInstallation. Its working fine. 

 

More info: https://issues.apache.org/jira/browse/SLING-5421 

View solution in original post