[
https://issues.apache.org/jira/browse/SLING-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15730412#comment-15730412
]
Alexander Klimetschek commented on SLING-5745:
----------------------------------------------
+1
We just had such a situation and doing these steps helped. In our case, after a
package install some bundles were not installed and were shown as
"Untransformed Resources" in /system/console/osgi-installer. Restarting the
bundle, the whole instance or reinstalling the package did not help.
We did these steps:
# stop {{org.apache.sling.installer.core}} bundle
# remove {{launchpad/installer/RegisteredResourceList.ser}} on the filesystem
(we kept a backup to be safe)
# start {{org.apache.sling.installer.core}} bundle again
> Provide a button to clear all registered entities and reinstall those
> ---------------------------------------------------------------------
>
> Key: SLING-5745
> URL: https://issues.apache.org/jira/browse/SLING-5745
> Project: Sling
> Issue Type: Improvement
> Components: Installer
> Affects Versions: Installer Console 1.0.2
> Reporter: Konrad Windszus
>
> Currently the web console at {{/system/console/osgi-installer}} exposes the
> history/state of the OSGi installer. In case the state is not reflecting
> reality for some reason, there should be a possibility to remove that history
> and restart the according bundles with a button inside that console.
> The actions which should be triggered under the hood should be
> # remove the data file {{RegisteredResourceList.ser}}
> # restart the bundle {{org.apache.sling.installer.core}}
> That should lead to every provider being asked about all entities which are
> then processed again so you end up with state again where the most
> prioritized entites are deployed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
