You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2014/10/10 11:56:34 UTC

[jira] [Closed] (SLING-3977) org.apache.sling.discovery.impl bundle gets deactivated

     [ https://issues.apache.org/jira/browse/SLING-3977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler closed SLING-3977.
-----------------------------------

> org.apache.sling.discovery.impl bundle gets deactivated
> -------------------------------------------------------
>
>                 Key: SLING-3977
>                 URL: https://issues.apache.org/jira/browse/SLING-3977
>             Project: Sling
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: Discovery Impl 1.0.10
>            Reporter: Timothee Maret
>            Assignee: Carsten Ziegeler
>             Fix For: Discovery Impl 1.0.12
>
>
> When removing the content under /var/discovery/impl, the org.apache.sling.discovery.impl bundle will be deactivated.
> Looking at the code, the org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler does deactivate the bundle when it detects two instances using the same sling.id in the same topology. This mechanism was implemented in SLING-2892, SLING-2901.
> When removing the content under /var/discovery/impl, the code will detect this as a having two instances with the same id and thus disable the bundle.
> Those two cases, should be differentiated.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)