[jira] [Commented] (FELIX-6048) Could not obtain lock
[ https://issues.apache.org/jira/browse/FELIX-6048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105424#comment-17105424 ] A. J. David Bosschaert commented on FELIX-6048: --- It would be really good if someone could post a testcase for this, if it's still reproducable... > 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.1.14 >Reporter: Alain Picard >Priority: Minor > Attachments: Felix no lock.png > > > 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 (v8.3.4#803005)
[jira] [Commented] (FELIX-6048) Could not obtain lock
[ https://issues.apache.org/jira/browse/FELIX-6048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17105429#comment-17105429 ] Alain Picard commented on FELIX-6048: - Not sure what changed at our end, but we are still on Felix 2.1.14.v20190123-1619 and have not seen that issue in a very long time. > 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.1.14 >Reporter: Alain Picard >Priority: Minor > Attachments: Felix no lock.png > > > 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 (v8.3.4#803005)
[jira] [Created] (FELIX-6274) Potential Class Space problems with multiple Log Service APIs
Timothy James Ward created FELIX-6274: - Summary: Potential Class Space problems with multiple Log Service APIs Key: FELIX-6274 URL: https://issues.apache.org/jira/browse/FELIX-6274 Project: Felix Issue Type: Bug Components: Declarative Services (SCR) Affects Versions: scr-2.1.20 Reporter: Timothy James Ward Fix For: scr-2.1.22 The Declarative Services specification requires SCR to inject Logger implementations into a DS component (if requested). In order to find a suitable Log Service SCR uses its *own* BundleContext, not the context of the bundle being extended. This means that if the bundle being extended has a different view of the Log Service API then the injection will fail with a ClassCastException. -- This message was sent by Atlassian Jira (v8.3.4#803005)