Dear Rupert and all,
unfortunately I can't see any error related to disk writing.
Here attached you can find the error log can you please help finding which
is the problem ?

I made the following :

1) clean stanbol folder
2) launch java -Xmx1g -jar -XX:MaxPermSize=128m
stanbol_src\launchers\full\target\org.apache.stanbol.launchers.full-0.10.0-SNAPSHOT.jar
3) once fully active ... stop the service with CTRL^C
4) wait for stopping the service
5) relaunch the same startup command
6) verify that entityhubExtraction enhancer is no more available

Thanks for your help.


Best,
Andrea






2012/11/15 Rupert Westenthaler <[email protected]>

> Hi
>
> On Thu, Nov 15, 2012 at 2:36 PM, Andrea Taurchini <[email protected]>
> wrote:
> > Dear All,
> > maybe I'm missing (again) something, but if I stop the framework, no
> matter
> > if through Felix Web Console or CTRL+C, configurations go to hell on the
> > next restart.
>
> No you are missing nothing. All those ways to shutdown Stanbol should
> work just fine. I can not remember having ever a problem like that.
>
> > Even the default enhancement chain will stop working since the order or
> the
> > engine is changed to :
> >
> >    - *metaxa* ( optional , currently not available)
> >    - *entityhubExtraction* ( required , currently not available)
> >    - *tika* ( optional , TikaEngine)
> >    - *langdetect* ( required , LanguageDetectionEnhancementEngine)
> >    - *ner* ( required , NamedEntityExtractionEnhancementEngine)
> >    - *dbpediaLinking* ( required , NamedEntityTaggingEngine)
> >
>
> that "not available" engines are listed first is expected for the
> WeightedChain. This chain determines the order based on information
> provided by the Engine. So if an Engine is not available such
> Information are not available. As the order does not matter for
> Engines that are not available my decision was to list them first.
>
> > not to mention the fact that my own configurations (topic classifier ...)
> > is completely removed ...
> >
>
> Somehow it looks like as OSGI is not able to write files to the disc.
> Can you please check the Stanbol log file
> {launcher-dir}/stanbol/logs/error.log if you can find related
> information.
>
> best
> Rupert
>
> > Thanks,
> > Andrea
>
>
>
> --
> | Rupert Westenthaler             [email protected]
> | Bodenlehenstraße 11                             ++43-699-11108907
> | A-5500 Bischofshofen
>

Reply via email to