felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FELIX-3714) Error when when fragment bundle is updated
Date Fri, 06 Dec 2013 10:15:36 GMT

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

Guillaume Nodet resolved FELIX-3714.
------------------------------------

       Resolution: Fixed
    Fix Version/s: fileinstall-3.2.8
         Assignee: Guillaume Nodet

Committing to https://svn.apache.org/repos/asf/felix/trunk ...
	M	fileinstall/src/main/java/org/apache/felix/fileinstall/internal/DirectoryWatcher.java
Committed r1548482


> Error when when fragment bundle is updated
> ------------------------------------------
>
>                 Key: FELIX-3714
>                 URL: https://issues.apache.org/jira/browse/FELIX-3714
>             Project: Felix
>          Issue Type: Bug
>          Components: File Install
>    Affects Versions: fileinstall-3.2.6
>            Reporter: Evgeniy Sedyshev
>            Assignee: Guillaume Nodet
>             Fix For: fileinstall-3.2.8
>
>
> On our project we have FileInstall watching a directory with bundles. One of those bundles
is a fragment. 
> When the fragment is modified (or deleted/created), we get the following error in the
log:
> 2012-10-17-13:20:53.406+0400 ERROR [Thread-17] org.apache.felix.fileinstall    In main
loop, we have serious trouble
> java.lang.NullPointerException: null
>         at org.apache.felix.fileinstall.internal.DirectoryWatcher.findBundlesWithFragmentsToRefresh(DirectoryWatcher.java:1273)
~[na:na]
>         at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:491)
~[na:na]
>         at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:291)
~[na:na]
> And what is more critical none of the other modified bundles becomes updated.
> The source of the NPE is 
> if (hostBundle.getSymbolicName().equals(path.getName()))  
> because there is no check here for SymbolicName being null.
> In our case the problem was in that there was a non-bundle jar inside osgi container
that therefore didn't have a SymbolicName, so we just removed it and that solved the problem.

> However, I strongly believe that there should be a check for not null in the mentioned
line.



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

Mime
View raw message