You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Rupert Westenthaler (JIRA)" <ji...@apache.org> on 2014/04/16 08:50:16 UTC

[jira] [Commented] (STANBOL-1304) entityhub/indexing/core/OsgiConfigurationUtil fail with npe

    [ https://issues.apache.org/jira/browse/STANBOL-1304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13970510#comment-13970510 ] 

Rupert Westenthaler commented on STANBOL-1304:
----------------------------------------------

regarding
        try {
             builder.addClasspath(new File(config.getDestinationFolder(),CONFIG_ROOT));
         } catch (IOException e) {
-            log.warn("Unable to build OSGI Bundle for Indexed Referenced Site "+config.getName(),e);
+            log.warn("(builder.addClasspath) Unable to build OSGI Bundle for Indexed Referenced Site "+config.getName(),e);
             builder.close();
+            //?? why not throwing an exception here ??
             return;

The reason why I decided to just log a WARN and not stop the process is that at this point the finallization phase has already done a lot of work (optimizing the SolrCore, building FST models, ...). So IMO it was better to notify the user why the bundle was not build while still continuing the "solrindex.zip" archive with the SolrCore.

> entityhub/indexing/core/OsgiConfigurationUtil fail with npe
> -----------------------------------------------------------
>
>                 Key: STANBOL-1304
>                 URL: https://issues.apache.org/jira/browse/STANBOL-1304
>             Project: Stanbol
>          Issue Type: Bug
>            Reporter: Florent ANDRE
>         Attachments: stanbol_1304.patch
>
>
> This make indexing utility not to create the osgi configuration bundle.
> The error [1] occured in generic rdf with specific configuration but also when running the entityhub/indexing/dbpedia utility following fetch_prepare.sh procedure with no modifications.
> Attached a unit test patch that reproduce the error.
> Reason is a little bit obscure as jar destination is good and writable.. bug from aQute lib ?
> [1]
> 01:53:17,539 [main] WARN  destination.OsgiConfigurationUtil - Unable to write OSGI Bundle for Indexed Referenced Site dbpedia
> java.lang.NullPointerException
> 	at aQute.lib.osgi.Jar.getResource(Jar.java:136)
> 	at aQute.lib.osgi.Jar.getManifest(Jar.java:171)
> 	at aQute.lib.osgi.Jar.writeManifest(Jar.java:252)
> 	at aQute.lib.osgi.Jar.doManifest(Jar.java:237)
> 	at aQute.lib.osgi.Jar.write(Jar.java:220)
> 	at aQute.lib.osgi.Jar.write(Jar.java:193)
> 	at org.apache.stanbol.entityhub.indexing.core.destination.OsgiConfigurationUtil.createBundle(OsgiConfigurationUtil.java:272)
> 	at org.apache.stanbol.entityhub.indexing.destination.solryard.SolrYardIndexingDestination.finalise(SolrYardIndexingDestination.java:739)
> 	at org.apache.stanbol.entityhub.indexing.core.impl.IndexerImpl.finaliseIndexing(IndexerImpl.java:552)
> 	at org.apache.stanbol.entityhub.indexing.core.impl.IndexerImpl.index(IndexerImpl.java:370)
> 	at org.apache.stanbol.entityhub.indexing.Main.main(Main.java:75)
> 01:53:17,542 [main] INFO  impl.IndexerImpl -   ...finalisation completed



--
This message was sent by Atlassian JIRA
(v6.2#6252)