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

Carsten Ziegeler commented on FELIX-6048:
-----------------------------------------

[~alpic80] Could you please retest with newer SCR versions like 2.1.16 or 
2.0.14?

> Could not obtain lock
> ---------------------
>
>                 Key: FELIX-6048
>                 URL: https://issues.apache.org/jira/browse/FELIX-6048
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services (SCR)
>    Affects Versions: scr-2.0.10
>            Reporter: Alain Picard
>            Priority: Minor
>
> I regularly get this exception when starting our app, w/o having ever seen 
> any impact.
>  
> {code:java}
> !ENTRY org.eclipse.equinox.cm 4 0 2019-02-02 14:31:46.715
> !MESSAGE Could not obtain lock
> !STACK 0
> java.lang.IllegalStateException: Could not obtain lock
>     at 
> org.apache.felix.scr.impl.manager.AbstractComponentManager.obtainLock(AbstractComponentManager.java:231)
>     at 
> org.apache.felix.scr.impl.manager.AbstractComponentManager.obtainActivationWriteLock(AbstractComponentManager.java:266)
>     at 
> org.apache.felix.scr.impl.manager.SingleComponentManager.reconfigure(SingleComponentManager.java:633)
>     at 
> org.apache.felix.scr.impl.manager.SingleComponentManager.reconfigure(SingleComponentManager.java:609)
>     at 
> org.apache.felix.scr.impl.manager.ConfigurableComponentHolder.configurationUpdated(ConfigurableComponentHolder.java:426)
>     at 
> org.apache.felix.scr.impl.manager.RegionConfigurationSupport.configurationEvent(RegionConfigurationSupport.java:284)
>     at 
> org.apache.felix.scr.impl.manager.RegionConfigurationSupport$1.configurationEvent(RegionConfigurationSupport.java:89)
>     at 
> org.eclipse.equinox.internal.cm.EventDispatcher$1.run(EventDispatcher.java:89)
>     at 
> org.eclipse.equinox.internal.cm.SerializedTaskQueue$1.run(SerializedTaskQueue.java:36)
> After reporting on OSGI forum, was suggested to report here.{code}



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

Reply via email to