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

Richard S. Hall reopened FELIX-2417:
------------------------------------


> NPE in Filter 
> --------------
>
>                 Key: FELIX-2417
>                 URL: https://issues.apache.org/jira/browse/FELIX-2417
>             Project: Felix
>          Issue Type: Bug
>    Affects Versions: framework-3.0.0
>         Environment: java version "1.6.0_20"
> Java(TM) SE Runtime Environment (build 1.6.0_20-b02)
> Java HotSpot(TM) Client VM (build 16.3-b01, mixed mode, sharing)
>            Reporter: Martin Zdila
>
> After upgrading framework from 2.0.5 to 3.0.0 I am getting many NPE 
> exceptions "Cannot register Component".
> I can't identify the core of the problem, but from what I see: in the 
> org.apache.felix.framework.FilterImpl on line 145 the name = 
> "service.factoryPid" but m_map doesn't contain such entry and so the key is 
> set to null. The next call on the line 147 fails because key cannot be null 
> in Hashtable.get(key).
> ERROR: my-cool-bundle (110): [my.cool.ServiceImpl] Cannot register Component
> java.lang.NullPointerException
>       at java.util.Hashtable.get(Hashtable.java:334)
>       at 
> org.apache.felix.framework.FilterImpl$DictionaryCapability.getAttribute(FilterImpl.java:147)
>       at 
> org.apache.felix.framework.capabilityset.CapabilitySet.matchesInternal(CapabilitySet.java:269)
>       at 
> org.apache.felix.framework.capabilityset.CapabilitySet.matches(CapabilitySet.java:226)
>       at org.apache.felix.framework.FilterImpl.match(FilterImpl.java:59)
>       at 
> org.apache.felix.cm.impl.ConfigurationManager.listConfigurations(ConfigurationManager.java:538)
>       at 
> org.apache.felix.cm.impl.ConfigurationAdminImpl.listConfigurations(ConfigurationAdminImpl.java:124)
>       at 
> org.apache.felix.scr.impl.config.ConfigurationComponentRegistry.findConfigurations(ConfigurationComponentRegistry.java:267)
>       at 
> org.apache.felix.scr.impl.config.ConfigurationComponentRegistry.findFactoryConfigurations(ConfigurationComponentRegistry.java:259)
>       at 
> org.apache.felix.scr.impl.config.ConfigurationComponentRegistry.createComponentHolder(ConfigurationComponentRegistry.java:107)
>       at 
> org.apache.felix.scr.impl.BundleComponentActivator.loadDescriptor(BundleComponentActivator.java:244)
>       at 
> org.apache.felix.scr.impl.BundleComponentActivator.initialize(BundleComponentActivator.java:147)
>       at 
> org.apache.felix.scr.impl.BundleComponentActivator.<init>(BundleComponentActivator.java:111)
>       at 
> org.apache.felix.scr.impl.Activator.loadComponents(Activator.java:255)
>       at org.apache.felix.scr.impl.Activator.bundleChanged(Activator.java:173)
>       at 
> org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:800)
>       at 
> org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:728)
>       at 
> org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:610)
>       at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:3734)
>       at org.apache.felix.framework.Felix.startBundle(Felix.java:1807)
>       at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1188)
>       at 
> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
>       at java.lang.Thread.run(Thread.java:619)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to