Re: [osgi-dev] SCR - Could not obtain lock
Thanks BJ, will do that. Alain On Mon, Feb 4, 2019 at 8:16 AM BJ Hargrave wrote: > You should report this to the Apache Felix SCR JIRA component. That is > where the Felix SCR developers can respond to the exception. > -- > > BJ Hargrave > Senior Technical Staff Member, IBM // office: +1 386 848 1781 > OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788 > hargr...@us.ibm.com > > > > - Original message - > From: Alain Picard via osgi-dev > Sent by: osgi-dev-boun...@mail.osgi.org > To: OSGi Developer Mail List > Cc: > Subject: [osgi-dev] SCR - Could not obtain lock > Date: Sat, Feb 2, 2019 2:36 PM > > I regularly get this exception when starting our app, w/o having ever seen > any impact. > > !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) > > IIRC I have seen forum threads to this effect, but is there anything that > we should do with this ? If it happens once the product is deployed that > doesn't look good and I hate putting exceptions under the rug. > > Please advise. > > Cheers, > Alain > > ___ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev > > > > ___ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
Re: [osgi-dev] SCR - Could not obtain lock
You should report this to the Apache Felix SCR JIRA component. That is where the Felix SCR developers can respond to the exception. --BJ HargraveSenior Technical Staff Member, IBM // office: +1 386 848 1781OSGi Fellow and CTO of the OSGi Alliance // mobile: +1 386 848 3788hargr...@us.ibm.com - Original message -From: Alain Picard via osgi-dev Sent by: osgi-dev-boun...@mail.osgi.orgTo: OSGi Developer Mail List Cc:Subject: [osgi-dev] SCR - Could not obtain lockDate: Sat, Feb 2, 2019 2:36 PM I regularly get this exception when starting our app, w/o having ever seen any impact. !ENTRY org.eclipse.equinox.cm 4 0 2019-02-02 14:31:46.715!MESSAGE Could not obtain lock!STACK 0java.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) IIRC I have seen forum threads to this effect, but is there anything that we should do with this ? If it happens once the product is deployed that doesn't look good and I hate putting exceptions under the rug. Please advise. Cheers, Alain ___OSGi Developer Mail Listosgi-dev@mail.osgi.orghttps://mail.osgi.org/mailman/listinfo/osgi-dev ___ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
[osgi-dev] SCR - Could not obtain lock
I regularly get this exception when starting our app, w/o having ever seen any impact. !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) IIRC I have seen forum threads to this effect, but is there anything that we should do with this ? If it happens once the product is deployed that doesn't look good and I hate putting exceptions under the rug. Please advise. Cheers, Alain ___ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
