felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FELIX-3390) Intermittent NPE in ConfigurationManager
Date Tue, 10 Apr 2012 06:17:21 GMT

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

Felix Meschberger resolved FELIX-3390.
--------------------------------------

       Resolution: Duplicate
    Fix Version/s: configadmin-1.4.0
         Assignee: Felix Meschberger

Since you declare this a duplicate of FELIX-2813 I close it as such.
                
> Intermittent NPE in ConfigurationManager
> ----------------------------------------
>
>                 Key: FELIX-3390
>                 URL: https://issues.apache.org/jira/browse/FELIX-3390
>             Project: Felix
>          Issue Type: Bug
>          Components: Configuration Admin
>    Affects Versions:  configadmin-1.2.8
>            Reporter: Marcel Offermans
>            Assignee: Felix Meschberger
>             Fix For: configadmin-1.4.0
>
>
> We are using Configuration Admin in our open source project, where we get the following
exception in our integration tests:
> {code}
> *ERROR* Unexpected problem executing task
> java.lang.NullPointerException: reference and pid must not be null
> 	at org.osgi.service.cm.ConfigurationEvent.<init>(ConfigurationEvent.java:120)
> 	at org.apache.felix.cm.impl.ConfigurationManager$FireConfigurationEvent.run(ConfigurationManager.java:1818)
> 	at org.apache.felix.cm.impl.UpdateThread.run(UpdateThread.java:104)
> 	at java.lang.Thread.run(Thread.java:662)
> {code}
> I'm not quite sure what is going on, and the NPE does not occur every time, but it does
seem to keep happening often enough to warrant a bug report as the code that is being executed
is not directly invoked by the test. For more background, look at (for example) this log:
> http://bamboo.amdatu.org/bamboo/browse/AMDATUPLATFORM-AMDATUGIT-JOB1-74/log
> At least some null checks would be in order, plus maybe a better log message that tells
us which of the two actually was null (I know this is an OSGi class that's doing the reporting,
but we could check ourselves before invoking its constructor).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message