You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Egli (JIRA)" <ji...@apache.org> on 2015/11/23 14:50:10 UTC
[jira] [Created] (SLING-5321) DiscoveryServiceImpl should have
mandatory dependency to SyncTokenService
Stefan Egli created SLING-5321:
----------------------------------
Summary: DiscoveryServiceImpl should have mandatory dependency to SyncTokenService
Key: SLING-5321
URL: https://issues.apache.org/jira/browse/SLING-5321
Project: Sling
Issue Type: Bug
Components: Extensions
Affects Versions: Discovery Impl 1.2.2
Reporter: Stefan Egli
Assignee: Stefan Egli
Fix For: Discovery Impl 1.2.4
Currently {{DiscoveryServiceImpl}} has an {{OPTIONAL_UNARY}} dependency to {{SyncTokenService}}. This has the effect that at {{DiscoveryServiceImpl.activate}} time, the {{SyncTokenService}} might not yet be set, but that it would be set at a later point in time.
Due to the fact that {{activate}} is the only time when this {{SyncTokenService}} is checked (depending on config) and set with the {{ViewStateManager}}, it will be missed and assumed to be not available in this case.
Which means you can have the sync token service available on one instance and not in another instance in the same cluster - leading to sync failure (where the only workaround is disabling the sync token service entirely)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)