This conversation has been locked due to inactivity. Please create a new post.
This conversation has been locked due to inactivity. Please create a new post.
Hi,
I'm having a bit of a problem importing a bundle and associated run mode config via vault in our prod environment (rightly of wrongly, but it works this way in other environments). Everything is deployed correctly under /apps (bundle jar is in /apps/<name>/install), but the bundle isn't present in the bundle list and there is nothing to suggest problems int he logs.
Looking at the components tab in the system console, there are a number of components with an ID of -1, including org.apache.sling.installer.provider.jcr.impl.JcrInstaller which is probably the root of my problem. Looking at the config entry for this it seems to be configured fine. The entry from the Declarative Services Components is as follows:
-1=[org.apache.sling.installer.provider.jcr.impl.JcrInstaller]
Bundleorg.apache.sling.installer.provider.jcr (5)
State=disabled
DefaultState=enabled
Activation=immediate
Reference=repository, Unsatisfied
Service Name: org.apache.sling.jcr.api.SlingRepository
Multiple: single
Optional: mandatory
Policy: static
No Services bound
Reference=settings, Unsatisfied
Service Name: org.apache.sling.settings.SlingSettingsService
Multiple: single
Optional: mandatory
Policy: static
No Services bound
Reference=installer, Unsatisfied
Service Name: org.apache.sling.installer.api.OsgiInstaller
Multiple: single
Optional: mandatory
Policy: static
No Services bound
Properties=
component.id=-1
component.name=org.apache.sling.installer.provider.jcr.impl.JcrInstaller
service.description=Sling Jcrinstall Service
service.pid=org.apache.sling.installer.provider.jcr.impl.JcrInstaller
service.vendor=The Apache Software Foundation
sling.jcrinstall.folder.max.depth=4
sling.jcrinstall.folder.name.regexp=.*/install$
sling.jcrinstall.search.path=[/libs:100, /apps:200]
All the unsatisfied references seem to be present, so I've no idea where to start to correct this.
Can anyone suggest why this component may be in this state?
Thanks in advance.
PS I'm running CQ5.4
Solved! Go to Solution.
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
Looks like bundle file is corrupted or for presence of earlier version the new installation may be ignored. Need complete logs & get assistance from official support.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies