[jira] [Resolved] (FELIX-4224) [DS] Dependency manager can be active but not have m_bindMethods set

["David Jencks (JIRA)" <ji...@apache.org>]

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

David Jencks resolved FELIX-4224.
---------------------------------

    Resolution: Fixed

m_bindMethods was made volatile in a commit for FELIX-4223

> [DS] Dependency manager can be active but not have m_bindMethods set
> --------------------------------------------------------------------
>
>                 Key: FELIX-4224
>                 URL: https://issues.apache.org/jira/browse/FELIX-4224
>             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
>
>
> We've seen an NPE from m_bindMethods being null in this code:
>         public void addedService( ServiceReference<T> serviceReference, RefPair<T> refPair, int trackingCount )
>         {
>             m_componentManager.log( LogService.LOG_DEBUG, "dm {0} tracking {1} MultipleDynamic added {2} (enter)", new Object[] {getName(), trackingCount, serviceReference}, null );
>         	boolean tracked = false;
>             if ( getPreviousRefMap().remove( serviceReference ) == null )
>             {
>                 if (isActive())
>                 {
>                     getServiceObject( m_bindMethods.getBind(), refPair );
> (DependencyManager.MultipleDynamicCustomizer, around line 314)
> After some investigation I can't see any way this can occur except from m_bindMethods not being volatile.  I'll see if this reoccurs after making it volatile.



--
This message was sent by Atlassian JIRA
(v6.1#6144)