[
https://issues.apache.org/jira/browse/FELIX-4171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13803355#comment-13803355
]
David Jencks commented on FELIX-4171:
-------------------------------------
Typical stack trace from a moderately recent build is
Caused by: java.lang.NullPointerException
at
org.apache.felix.scr.impl.manager.DependencyManager.invokeUnbindMethod(DependencyManager.java:1727)
at
org.apache.felix.scr.impl.manager.DependencyManager.close(DependencyManager.java:1487)
at
org.apache.felix.scr.impl.manager.ImmediateComponentManager.createImplementationObject(ImmediateComponentManager.java:290)
at
org.apache.felix.scr.impl.manager.ImmediateComponentManager.createComponent(ImmediateComponentManager.java:127)
at
org.apache.felix.scr.impl.manager.ImmediateComponentManager.getService(ImmediateComponentManager.java:855)
at
org.apache.felix.scr.impl.manager.ImmediateComponentManager.getServiceInternal(ImmediateComponentManager.java:822)
at
org.apache.felix.scr.impl.manager.ImmediateComponentManager.getService(ImmediateComponentManager.java:761)
> [DS] possible DependencyManager NPE during cleanup after failure to activate
> a component
> ----------------------------------------------------------------------------------------
>
> Key: FELIX-4171
> URL: https://issues.apache.org/jira/browse/FELIX-4171
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR)
> Affects Versions: scr-1.8.0
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: scr-1.8.0
>
>
> Thanks to Adam Purkiss for finding and reporting this problem.
> If a component has more than one dependency, and a non-last dependency cannot
> actually be obtained during activation, we'll try to close the non-opened
> dependency managers: their EdgeInfo wont have the openLatch set (they aren't
> open) and the attempt to use the latch during close will cause an NPE.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
