You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2018/10/06 08:05:00 UTC

[jira] [Commented] (FELIX-5953) Circular reference error

    [ https://issues.apache.org/jira/browse/FELIX-5953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16640615#comment-16640615 ] 

Carsten Ziegeler commented on FELIX-5953:
-----------------------------------------

[~bdaniel] This looks like the same problem as described in FELIX-4260 . We have included a fix for this in the latest scr-2.1.10 release which will be out soon. Could you please test with that version?

> Circular reference error
> ------------------------
>
>                 Key: FELIX-5953
>                 URL: https://issues.apache.org/jira/browse/FELIX-5953
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services (SCR)
>    Affects Versions: scr-2.1.6
>            Reporter: Brent Daniel
>            Priority: Minor
>
> If the call to obtainStateLock SingleComponentManager.getService doesn't succeed, an IllegalStateException will be thrown which will result in ComponentRegistry.leaveCreate() not being called. That leaves circularInfos in ComponentRegistry in an invalid state which will result in the error "Circular reference detected trying to get service". 
> We typically see this when a component has a long running activator running in one thread and another thread tries to get a service from a reference and ends up eventually timing out in SingleComponentManager.getService because the other thread holds the lock. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)