[ https://issues.apache.org/jira/browse/SLING-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12909162#action_12909162 ]
Carsten Ziegeler commented on SLING-1737: ----------------------------------------- This might be a sync problem in the OsgiInstallerImpl - Felix reported that he got similar errors while running the tests under load. Looking at the OsgiInstallerImpl it can definitly run into a deadlock (this bug has been there forever, but is more prominent now), so once I can reproduce, I'll try to fix this sync problem > Add state management for resources > ---------------------------------- > > Key: SLING-1737 > URL: https://issues.apache.org/jira/browse/SLING-1737 > Project: Sling > Issue Type: Improvement > Components: Installer > Affects Versions: OSGi Installer 3.0.0 > Reporter: Carsten Ziegeler > Assignee: Carsten Ziegeler > Fix For: OSGi Installer 3.0.0 > > Attachments: ConfigInstallTest-debug.log.gz, debug.zip, > RemovedResourceDetectionTest-debug.log.gz > > > Currently there is no state management, so it is hard to tell if a resource > has been installed, should be installed, uninstalled etc. > In some situations this leads to endless loops where something is tried over > and over again - although nothing needs to be done anymore or can't be done. > If we add proper state management to the resources, the installer knows what > needs to be done and can act accordingly -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.