[jira] [Commented] (SLING-5745) Provide a button to clear all registered entities and reinstall those
[
https://issues.apache.org/jira/browse/SLING-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16531616#comment-16531616
]
Konrad Windszus commented on SLING-5745:
This workaround is no longer recommended, because you no longer get the correct
state in the OSGi Installer, because bundles which are already installed in the
same version are just marked as "IGNORED" instead of "INSTALLED"
(https://github.com/apache/sling-org-apache-sling-installer-core/blob/1561f5e626bab4859b4c060ef1bec06026018f18/src/main/java/org/apache/sling/installer/core/impl/tasks/BundleTaskCreator.java#L280)
because they are already deployed in Felix in the same version.
> 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
>Priority: Major
>
> 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
(v7.6.3#76005)
[jira] [Commented] (SLING-5745) Provide a button to clear all registered entities and reinstall those
[
https://issues.apache.org/jira/browse/SLING-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16524950#comment-16524950
]
Konrad Windszus commented on SLING-5745:
Actually, it is currently possible to manually overwrite the configuration or
the bundle (with the Web Console) without the OSGi Installer noticing it
(SLING-7736). In that case it would be helpful to just reinstall the
configuration/bundles from the OSGi Installer.
> 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
>Priority: Major
>
> 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
(v7.6.3#76005)
[jira] [Commented] (SLING-5745) Provide a button to clear all registered entities and reinstall those
[
https://issues.apache.org/jira/browse/SLING-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15732716#comment-15732716
]
Alexander Klimetschek commented on SLING-5745:
--
Unfortunately we could not find any hint on what was going wrong. Only thing
was that we had 4.1.0-snapshot bundles before and went to a 4.1.0 release,
however, the entire tree was replaced in the package and both jars never were
present at the same time in the JCR. In many cases it works fine.
IIUC, the installer logic is pretty complex. Until it's 100% perfect, a "Reset
cache" operation seems useful. Sometimes getting things to work is more time
critical than understanding it fully.
> 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)
[jira] [Commented] (SLING-5745) Provide a button to clear all registered entities and reinstall those
[
https://issues.apache.org/jira/browse/SLING-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15731513#comment-15731513
]
Felix Meschberger commented on SLING-5745:
--
Nice workaround, but ...
Why is the state corrupt in the first place ? I strongly suggest to fix the
problem and hold back with symptom touching on a broad basis.
If we cannot make the state stable, the bundle must be modified to deal with
corrupt state.
> 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)
[jira] [Commented] (SLING-5745) Provide a button to clear all registered entities and reinstall those
[
https://issues.apache.org/jira/browse/SLING-5745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
