You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stanbol.apache.org by Gianluigi Di Vito <gi...@kit-digital.com> on 2013/02/14 16:22:56 UTC
Enhancement Chain failed
Hi all,
I have a problem with Stanbol Enhancer, when I try to call it returns always the same error:
org.apache.stanbol.enhancer.servicesapi.ChainException: Enhancement Chain failed because of required Engine 'dbpediaLinking' failed
I'm using the fullwar version (revision: 1446191) deployed under Tomcat 5.5 on a Windows machine.
The error is showed both if I use a web view and if I call through the rest api.
Many thanks.
Gianluigi
Below the full log:
Enhancement Process Metadata:
Execution of Chain default failed in 5.06sec.
unknown: scheduled in [duration not available] : entityhubExtraction ( required , start: unknown, completion: unknown)
15-59-49.472: completed in 0ms : tika ( optional , start: 15-59-49.472, completion: 15-59-49.472)
15-59-49.488: completed in 0ms : langdetect ( required , start: 15-59-49.488, completion: 15-59-49.488)
15-59-49.488: completed in 15ms : opennlp-sentence ( required , start: 15-59-49.488, completion: 15-59-49.503)
15-59-49.503: completed in 32ms : opennlp-ner ( required , start: 15-59-49.503, completion: 15-59-49.535)
15-59-49.503: completed in 0ms : opennlp-pos ( required , start: 15-59-49.503, completion: 15-59-49.503)
15-59-49.503: completed in 0ms : opennlp-token ( required , start: 15-59-49.503, completion: 15-59-49.503)
15-59-49.535: failed in 5.00sec : dbpediaLinking ( required , start: 15-59-49.535, completion: 15-59-54.535)
OUTPUT:
org.apache.stanbol.enhancer.servicesapi.ChainException: Enhancement Chain failed because of required Engine 'dbpediaLinking' failed with Message: Unable to process ContentItem '<urn:content-item-sha1-37c8a8244041cf6113d4ee04b3a04d0a014f6e10>' with Enhancement Engine 'dbpediaLinking' because the engine was unable to process the content (Engine class: org.apache.stanbol.enhancer.engines.entitytagging.impl.NamedEntityTaggingEngine)(Reason: Unable to initialize the Cache with Yard dbpediaIndex! This is usually caused by Errors while reading the Cache Configuration from the Yard.)!
at org.apache.stanbol.enhancer.jobmanager.event.impl.EventJobManagerImpl.enhanceContent(EventJobManagerImpl.java:179)
at org.apache.stanbol.enhancer.jersey.resource.AbstractEnhancerResource.enhance(AbstractEnhancerResource.java:233)
at org.apache.stanbol.enhancer.jersey.resource.AbstractEnhancerUiResource.enhanceFromForm(AbstractEnhancerUiResource.java:126)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$ResponseOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:205)
at com.sun.jersey.server.impl.model.method.dispatch.ResourceJavaMethodDispatcher.dispatch(ResourceJavaMethodDispatcher.java:75)
at com.sun.jersey.server.impl.uri.rules.HttpMethodRule.accept(HttpMethodRule.java:302)
at com.sun.jersey.server.impl.uri.rules.ResourceClassRule.accept(ResourceClassRule.java:108)
at com.sun.jersey.server.impl.uri.rules.RightHandPathRule.accept(RightHandPathRule.java:147)
at com.sun.jersey.server.impl.uri.rules.RootResourceClassesRule.accept(RootResourceClassesRule.java:84)
at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1480)
at com.sun.jersey.server.impl.application.WebApplicationImpl._handleRequest(WebApplicationImpl.java:1411)
at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1360)
at com.sun.jersey.server.impl.application.WebApplicationImpl.handleRequest(WebApplicationImpl.java:1350)
at com.sun.jersey.spi.container.servlet.WebComponent.service(WebComponent.java:416)
at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:538)
at com.sun.jersey.spi.container.servlet.ServletContainer.service(ServletContainer.java:716)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.felix.http.base.internal.handler.ServletHandler.doHandle(ServletHandler.java:96)
at org.apache.felix.http.base.internal.handler.ServletHandler.handle(ServletHandler.java:79)
at org.apache.felix.http.base.internal.dispatch.ServletPipeline.handle(ServletPipeline.java:42)
at org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:49)
at org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33)
at org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:78)
at org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:47)
at org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33)
at org.apache.stanbol.commons.httpqueryheaders.impl.QueryHeadersFilter.doFilter(QueryHeadersFilter.java:75)
at org.apache.felix.http.base.internal.handler.FilterHandler.doHandle(FilterHandler.java:88)
at org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:76)
at org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:47)
at org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33)
at org.apache.stanbol.commons.web.resources.ResourceServingFilter.doFilterHttp(ResourceServingFilter.java:148)
at org.apache.stanbol.commons.web.resources.ResourceServingFilter.doFilter(ResourceServingFilter.java:91)
at org.apache.felix.http.base.internal.handler.FilterHandler.doHandle(FilterHandler.java:88)
at org.apache.felix.http.base.internal.handler.FilterHandler.handle(FilterHandler.java:76)
at org.apache.felix.http.base.internal.dispatch.InvocationFilterChain.doFilter(InvocationFilterChain.java:47)
at org.apache.felix.http.base.internal.dispatch.HttpFilterChain.doFilter(HttpFilterChain.java:33)
at org.apache.felix.http.base.internal.dispatch.FilterPipeline.dispatch(FilterPipeline.java:48)
at org.apache.felix.http.base.internal.dispatch.Dispatcher.dispatch(Dispatcher.java:39)
at org.apache.felix.http.base.internal.DispatcherServlet.service(DispatcherServlet.java:67)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.felix.http.proxy.ProxyServlet.service(ProxyServlet.java:60)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.sling.launchpad.base.webapp.SlingServletDelegate.service(SlingServletDelegate.java:278)
at org.apache.sling.launchpad.webapp.SlingServlet.service(SlingServlet.java:174)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.netbeans.modules.web.monitor.server.MonitorFilter.doFilter(MonitorFilter.java:393)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:861)
at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:579)
at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1584)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.IllegalStateException: Unable to initialize the Cache with Yard dbpediaIndex! This is usually caused by Errors while reading the Cache Configuration from the Yard.
at org.apache.stanbol.entityhub.core.site.CacheImpl.getCacheYard(CacheImpl.java:220)
at org.apache.stanbol.entityhub.core.site.CacheImpl.getQueryFactory(CacheImpl.java:362)
at org.apache.stanbol.entityhub.core.impl.ReferencedSiteImpl.getQueryFactory(ReferencedSiteImpl.java:602)
at org.apache.stanbol.enhancer.engines.entitytagging.impl.NamedEntityTaggingEngine.computeEntityRecommentations(NamedEntityTaggingEngine.java:445)
at org.apache.stanbol.enhancer.engines.entitytagging.impl.NamedEntityTaggingEngine.computeEnhancements(NamedEntityTaggingEngine.java:370)
at org.apache.stanbol.enhancer.jobmanager.event.impl.EnhancementJobHandler.processEvent(EnhancementJobHandler.java:271)
at org.apache.stanbol.enhancer.jobmanager.event.impl.EnhancementJobHandler.handleEvent(EnhancementJobHandler.java:189)
at org.apache.felix.eventadmin.impl.tasks.HandlerTaskImpl.execute(HandlerTaskImpl.java:88)
at org.apache.felix.eventadmin.impl.tasks.SyncDeliverTasks.execute(SyncDeliverTasks.java:221)
at org.apache.felix.eventadmin.impl.tasks.AsyncDeliverTasks$TaskExecuter.run(AsyncDeliverTasks.java:110)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
... 1 more
Caused by: org.apache.stanbol.entityhub.servicesapi.yard.YardException: The SolrIndex 'dbpedia' for SolrYard 'dbpedia default data index' is currently not active!
at org.apache.stanbol.entityhub.yard.solr.impl.SolrYard.getServer(SolrYard.java:555)
at org.apache.stanbol.entityhub.yard.solr.impl.SolrYard.getRepresentation(SolrYard.java:935)
at org.apache.stanbol.entityhub.core.site.CacheUtils.loadBaseMappings(CacheUtils.java:56)
at org.apache.stanbol.entityhub.core.site.CacheImpl.initWithCacheYard(CacheImpl.java:120)
at org.apache.stanbol.entityhub.core.site.CacheImpl.getCacheYard(CacheImpl.java:216)
... 11 more
Gianluigi Di Vito | Software Engineer, R&D
+39 02 84278 465 Office | gianluigi.di.vito Skype
KIT digital | www.kitd.com<http://www.kitd.com/> | The Future of Television
Milan Office | Via Breda, 176 | 20126 Milano, Italy
[cid:266E708A-798C-4FCC-8CE5-E48CB9EBF17F]
Re: Enhancement Chain failed
Posted by Rupert Westenthaler <ru...@gmail.com>.
Hi,
My fix introduced an other issue with String.split(File.seperator)
being '\' on windows as the split(..) method expects REGEX and '\'
needs to be escaped. WIth [1] revision 1447860 I changed the
implementation so that String.split is no longer used. Can you please
check if the initialization now works as expected.
best
Rupert
[1] http://svn.apache.org/r1447860
On Tue, Feb 19, 2013 at 3:03 PM, Gianluigi Di Vito
<gi...@kit-digital.com> wrote:
> Hi,
> I applied the patch (in both ways) but unfortunately it didn't fixed the problem.
>
> You can find the log file at this address:
> https://dl.dropbox.com/u/11432141/newerror.log
>
>
> Gianluigi Di Vito | Software Engineer, R&D
> +39 02 84278 465 Office | gianluigi.divito Skype
>
> KIT digital | www.kitd.com | The Future of Television
> Milan Office | Via Breda, 176 | 20126 Milano, Italy
>
>
>
> -----Original Message-----
> From: Rupert Westenthaler [mailto:rupert.westenthaler@gmail.com]
> Sent: martedì 19 febbraio 2013 12:50
> To: dev@stanbol.apache.org
> Subject: Re: Enhancement Chain failed
>
> Hi
>
> with revision 1447686 [1] I provided a patch that should fix your problem. To apply this patch you can
>
> svn update
> cd commons/solr/core
>
> than assuming that Stanbol is currently running on localhost:8080 and the System Console password is still the default
>
> mvn clean install -P installBundle
> -Dsling.url=http://localhost:8080/system/console
>
> after that the ManageSolrServer should be initialized correctly. I do not think that a restart is required, but maybe I am wrong.
>
> As alternatives you can also make a clean build of the whole system or just build "commons/solr/core" and than install the bundle (will be in the "./target" folder) via the Bundle Tab of the Felix Webconsole
> (http://localhost:8080/system/console/bundles)
>
> best
> Rupert
>
>
> [1] http://svn.apache.org/r1447686
--
| Rupert Westenthaler rupert.westenthaler@gmail.com
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen
RE: Enhancement Chain failed
Posted by Gianluigi Di Vito <gi...@kit-digital.com>.
Hi,
I applied the patch (in both ways) but unfortunately it didn't fixed the problem.
You can find the log file at this address:
https://dl.dropbox.com/u/11432141/newerror.log
Gianluigi Di Vito | Software Engineer, R&D
+39 02 84278 465 Office | gianluigi.divito Skype
KIT digital | www.kitd.com | The Future of Television
Milan Office | Via Breda, 176 | 20126 Milano, Italy
-----Original Message-----
From: Rupert Westenthaler [mailto:rupert.westenthaler@gmail.com]
Sent: martedì 19 febbraio 2013 12:50
To: dev@stanbol.apache.org
Subject: Re: Enhancement Chain failed
Hi
with revision 1447686 [1] I provided a patch that should fix your problem. To apply this patch you can
svn update
cd commons/solr/core
than assuming that Stanbol is currently running on localhost:8080 and the System Console password is still the default
mvn clean install -P installBundle
-Dsling.url=http://localhost:8080/system/console
after that the ManageSolrServer should be initialized correctly. I do not think that a restart is required, but maybe I am wrong.
As alternatives you can also make a clean build of the whole system or just build "commons/solr/core" and than install the bundle (will be in the "./target" folder) via the Bundle Tab of the Felix Webconsole
(http://localhost:8080/system/console/bundles)
best
Rupert
[1] http://svn.apache.org/r1447686
Re: Enhancement Chain failed
Posted by Rupert Westenthaler <ru...@gmail.com>.
Hi
with revision 1447686 [1] I provided a patch that should fix your
problem. To apply this patch you can
svn update
cd commons/solr/core
than assuming that Stanbol is currently running on localhost:8080 and
the System Console password is still the default
mvn clean install -P installBundle
-Dsling.url=http://localhost:8080/system/console
after that the ManageSolrServer should be initialized correctly. I do
not think that a restart is required, but maybe I am wrong.
As alternatives you can also make a clean build of the whole system or
just build "commons/solr/core" and than install the bundle (will be in
the "./target" folder) via the Bundle Tab of the Felix Webconsole
(http://localhost:8080/system/console/bundles)
best
Rupert
[1] http://svn.apache.org/r1447686
On Tue, Feb 19, 2013 at 12:27 PM, Rupert Westenthaler
<ru...@gmail.com> wrote:
> Hi Gianluigi,
>
> thanks for the log file! You problem is caused by a bug in the
> initialization of the ManagedSolrServer on Windows. I created
> STANBOL-945 [1] with a detailed description. I plan to provide a patch
> later today. Would be nice if you could validate that it solves the
> problem.
>
> best
> Rupert
>
> [1] https://issues.apache.org/jira/browse/STANBOL-945
>
> On Tue, Feb 19, 2013 at 11:39 AM, Gianluigi Di Vito
> <gi...@kit-digital.com> wrote:
>> Sorry,
>> probably I forgot the attachment, anyway it is possible to download it at this address:
>> http://dl.dropbox.com/u/11432141/error.log
>>
>> Gianluigi Di Vito | Software Engineer, R&D
>> +39 02 84278 465 Office | gianluigi.divito Skype
>>
>> KIT digital | www.kitd.com | The Future of Television
>> Milan Office | Via Breda, 176 | 20126 Milano, Italy
>>
>>
>>
>>
>> -----Original Message-----
>> From: Gianluigi Di Vito
>> Sent: martedì 19 febbraio 2013 11:11
>> To: dev@stanbol.apache.org
>> Subject: RE: Enhancement Chain failed
>>
>> Hello Rupert,
>> thanks for your reply, in order to exclude most of the problems I have recreated a new instance of Apache Stanbol following all the steps in "Getting Start" page.
>>
>> I run the stable launcher from my local machine but it doesn't works, I have always the same error when I call the enhancer engine.
>> I have started the stable version with:
>> java -Xmx1g -jar org.apache.stanbol.launchers.stable-0.10.0-SNAPSHOT.jar -p9090 and I used the enhancer engine with the "standard" phrase: " The Stanbol enhancer can detect famous cities such as Paris and people such as Bob Marley."
>>
>> As you wrote me I have checked the "dbpedia.solrindex.ref" file in the "{working-dir}/stanbol/felix/bundle??/data/.config/index-config/*" but I didn't found the data folder under the bundle folder.
>> I have tried, in the felix web console, to stop and start the "org.apache.stanbol.data.sites.dbpedia" but never change.
>>
>> As attachment you can find the log file, as additional information I report my configuration
>>
>> Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100) Maven home: C:\Program Files\apache-maven-3.0.4\bin\..
>> Java version: 1.6.0_13, vendor: Sun Microsystems Inc.
>> Java home: C:\Program Files\Java\jdk1.6.0_13\jre Default locale: it_IT, platform encoding: Cp1252 OS name: "windows vista", version: "6.1", arch: "x86", family: "windows"
>> Stable Path: D:\Documenti\Progetti\IKS\LastVersion\launchers\stable\target
>>
>> I hope these can be useful to find a solution, Many Thanks
>>
>> Gianluigi
>
>
>
> --
> | Rupert Westenthaler rupert.westenthaler@gmail.com
> | Bodenlehenstraße 11 ++43-699-11108907
> | A-5500 Bischofshofen
--
| Rupert Westenthaler rupert.westenthaler@gmail.com
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen
Re: Enhancement Chain failed
Posted by Rupert Westenthaler <ru...@gmail.com>.
Hi Gianluigi,
thanks for the log file! You problem is caused by a bug in the
initialization of the ManagedSolrServer on Windows. I created
STANBOL-945 [1] with a detailed description. I plan to provide a patch
later today. Would be nice if you could validate that it solves the
problem.
best
Rupert
[1] https://issues.apache.org/jira/browse/STANBOL-945
On Tue, Feb 19, 2013 at 11:39 AM, Gianluigi Di Vito
<gi...@kit-digital.com> wrote:
> Sorry,
> probably I forgot the attachment, anyway it is possible to download it at this address:
> http://dl.dropbox.com/u/11432141/error.log
>
> Gianluigi Di Vito | Software Engineer, R&D
> +39 02 84278 465 Office | gianluigi.divito Skype
>
> KIT digital | www.kitd.com | The Future of Television
> Milan Office | Via Breda, 176 | 20126 Milano, Italy
>
>
>
>
> -----Original Message-----
> From: Gianluigi Di Vito
> Sent: martedì 19 febbraio 2013 11:11
> To: dev@stanbol.apache.org
> Subject: RE: Enhancement Chain failed
>
> Hello Rupert,
> thanks for your reply, in order to exclude most of the problems I have recreated a new instance of Apache Stanbol following all the steps in "Getting Start" page.
>
> I run the stable launcher from my local machine but it doesn't works, I have always the same error when I call the enhancer engine.
> I have started the stable version with:
> java -Xmx1g -jar org.apache.stanbol.launchers.stable-0.10.0-SNAPSHOT.jar -p9090 and I used the enhancer engine with the "standard" phrase: " The Stanbol enhancer can detect famous cities such as Paris and people such as Bob Marley."
>
> As you wrote me I have checked the "dbpedia.solrindex.ref" file in the "{working-dir}/stanbol/felix/bundle??/data/.config/index-config/*" but I didn't found the data folder under the bundle folder.
> I have tried, in the felix web console, to stop and start the "org.apache.stanbol.data.sites.dbpedia" but never change.
>
> As attachment you can find the log file, as additional information I report my configuration
>
> Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100) Maven home: C:\Program Files\apache-maven-3.0.4\bin\..
> Java version: 1.6.0_13, vendor: Sun Microsystems Inc.
> Java home: C:\Program Files\Java\jdk1.6.0_13\jre Default locale: it_IT, platform encoding: Cp1252 OS name: "windows vista", version: "6.1", arch: "x86", family: "windows"
> Stable Path: D:\Documenti\Progetti\IKS\LastVersion\launchers\stable\target
>
> I hope these can be useful to find a solution, Many Thanks
>
> Gianluigi
--
| Rupert Westenthaler rupert.westenthaler@gmail.com
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen
RE: Enhancement Chain failed
Posted by Gianluigi Di Vito <gi...@kit-digital.com>.
Sorry,
probably I forgot the attachment, anyway it is possible to download it at this address:
http://dl.dropbox.com/u/11432141/error.log
Gianluigi Di Vito | Software Engineer, R&D
+39 02 84278 465 Office | gianluigi.divito Skype
KIT digital | www.kitd.com | The Future of Television
Milan Office | Via Breda, 176 | 20126 Milano, Italy
-----Original Message-----
From: Gianluigi Di Vito
Sent: martedì 19 febbraio 2013 11:11
To: dev@stanbol.apache.org
Subject: RE: Enhancement Chain failed
Hello Rupert,
thanks for your reply, in order to exclude most of the problems I have recreated a new instance of Apache Stanbol following all the steps in "Getting Start" page.
I run the stable launcher from my local machine but it doesn't works, I have always the same error when I call the enhancer engine.
I have started the stable version with:
java -Xmx1g -jar org.apache.stanbol.launchers.stable-0.10.0-SNAPSHOT.jar -p9090 and I used the enhancer engine with the "standard" phrase: " The Stanbol enhancer can detect famous cities such as Paris and people such as Bob Marley."
As you wrote me I have checked the "dbpedia.solrindex.ref" file in the "{working-dir}/stanbol/felix/bundle??/data/.config/index-config/*" but I didn't found the data folder under the bundle folder.
I have tried, in the felix web console, to stop and start the "org.apache.stanbol.data.sites.dbpedia" but never change.
As attachment you can find the log file, as additional information I report my configuration
Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100) Maven home: C:\Program Files\apache-maven-3.0.4\bin\..
Java version: 1.6.0_13, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_13\jre Default locale: it_IT, platform encoding: Cp1252 OS name: "windows vista", version: "6.1", arch: "x86", family: "windows"
Stable Path: D:\Documenti\Progetti\IKS\LastVersion\launchers\stable\target
I hope these can be useful to find a solution, Many Thanks
Gianluigi
RE: Enhancement Chain failed
Posted by Gianluigi Di Vito <gi...@kit-digital.com>.
Hello Rupert,
thanks for your reply, in order to exclude most of the problems I have recreated a new instance of Apache Stanbol following all the steps in "Getting Start" page.
I run the stable launcher from my local machine but it doesn't works, I have always the same error when I call the enhancer engine.
I have started the stable version with:
java -Xmx1g -jar org.apache.stanbol.launchers.stable-0.10.0-SNAPSHOT.jar -p9090 and I used the enhancer engine with the "standard" phrase: " The Stanbol enhancer can detect famous cities such as Paris and people such as Bob Marley."
As you wrote me I have checked the "dbpedia.solrindex.ref" file in the "{working-dir}/stanbol/felix/bundle??/data/.config/index-config/*" but I didn't found the data folder under the bundle folder.
I have tried, in the felix web console, to stop and start the "org.apache.stanbol.data.sites.dbpedia" but never change.
As attachment you can find the log file, as additional information I report my configuration
Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Maven home: C:\Program Files\apache-maven-3.0.4\bin\..
Java version: 1.6.0_13, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_13\jre
Default locale: it_IT, platform encoding: Cp1252
OS name: "windows vista", version: "6.1", arch: "x86", family: "windows"
Stable Path: D:\Documenti\Progetti\IKS\LastVersion\launchers\stable\target
I hope these can be useful to find a solution,
Many Thanks
Gianluigi
Re: Enhancement Chain failed
Posted by Rupert Westenthaler <ru...@gmail.com>.
Hi Gianluigi
Sorry for the late replay, but I was offline the last few days.
On Thu, Feb 14, 2013 at 4:22 PM, Gianluigi Di Vito
<gi...@kit-digital.com> wrote:
>
> Caused by: java.lang.IllegalStateException: Unable to initialize the Cache with Yard dbpediaIndex! This is usually caused by Errors while reading the Cache Configuration from the Yard.
> at org.apache.stanbol.entityhub.core.site.CacheImpl.getCacheYard(CacheImpl.java:220)
This Exception indicates that the initialization of the SolrCore for
the DBpedia.org local index has failed. When this happens you should
see some releated error messages in the error.log file (usually
printed during startup, or shortly after you copied the
dbpedia.solrindex.zip file in the datafiles folder.
You can also look for a file named "dbpedia.solrindex.ref" file within
the "{working-dir}/stanbol/felix/bundle??/data/.config/index-config/*"
(where "bundle??" will be the ID of the
org.apache.stanbol.commons.solr.managed bundle). Under Linux I use
"find . -name "*.solrindex.ref" to get the location o the file. This
file will also contain the stacktrace on any error thrown during the
initialization.
To force a reinitialization of the dbpedia index you can also
stop/start the "org.apache.stanbol.data.sites.dbpedia" bundle e.g. by
using the the Bundle Tab of the felix webconsole
(http://localhost:8080/system/console/bundles).
I fixed already several Windows related issues but there might be
still some more. Based on the experience of previous cases I would
like to ask you some questions:
* are there any special chars in the path to the Stanbol instances (e.g. spaces)
* have you created your own dbpedia index, or downloaded a existing version
* if yes, what platform (windows or linux/mac) have you used to create the index
To find more details about this it would be nice if you could provide
the logs of a stanbol startup.
best
Rupert
--
| Rupert Westenthaler rupert.westenthaler@gmail.com
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen