You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stanbol.apache.org by Apache Hudson Server <hu...@hudson.apache.org> on 2011/02/12 22:52:05 UTC
Hudson build became unstable: stanbol-trunk-1.6 » Apache Stanbol Enhancer Integration Tests #15
See <https://hudson.apache.org/hudson/job/stanbol-trunk-1.6/org.apache.stanbol$org.apache.stanbol.enhancer.integration-tests/15/>
Hudson build is back to stable : stanbol-trunk-1.6 » Apache Stanbol Enhancer Integration Tests #17
Posted by Apache Hudson Server <hu...@hudson.apache.org>.
See <https://hudson.apache.org/hudson/job/stanbol-trunk-1.6/org.apache.stanbol$org.apache.stanbol.enhancer.integration-tests/17/>
Hudson build is still unstable: stanbol-trunk-1.6 » Apache Stanbol Enhancer Integration Tests #16
Posted by Apache Hudson Server <hu...@hudson.apache.org>.
See <https://hudson.apache.org/hudson/job/stanbol-trunk-1.6/org.apache.stanbol$org.apache.stanbol.enhancer.integration-tests/16/>
Re: Hudson build became unstable: stanbol-trunk-1.6 » Apache Stanbol Enhancer Integration Tests #15
Posted by Olivier Grisel <ol...@ensta.org>.
2011/2/13 Rupert Westenthaler <ru...@gmail.com>:
> Hi
>
> after some digging I found the reason for this is the unavailability
> of the geonames.org webserivce
>
> see this section in the log
>
> Caused by: java.io.IOException: Server returned HTTP response code:
> 503 for URL: http://ws.geonames.org/search?name=Paris&maxRows=5&type=json&style=FULL
> at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1313)
> at org.apache.stanbol.enhancer.engines.geonames.impl.GeonamesAPIWrapper.searchToponyms(GeonamesAPIWrapper.java:358)
> at org.apache.stanbol.enhancer.engines.geonames.impl.LocationEnhancementEngine.computeEnhancements(LocationEnhancementEngine.java:292)
> ... 42 more
>
> I suggest to deactivate all engines that depend on external service
> for the integration builds. However I have no Idea how to do that
> other than creating an own sling launcher configuration that excludes
> such engines.
A launcher for off-line stanbol is a good idea anyway: it would be
useful for people pre-loading the entithub with precomputed entity
dumps and only use enhancements related to this local base without
relying on an internet connection to remote services and / or
knowledge bases.
--
Olivier
http://twitter.com/ogrisel - http://github.com/ogrisel
Re: Hudson build became unstable: stanbol-trunk-1.6 » Apache Stanbol Enhancer Integration Tests #15
Posted by Rupert Westenthaler <ru...@gmail.com>.
Hi
after some digging I found the reason for this is the unavailability
of the geonames.org webserivce
see this section in the log
Caused by: java.io.IOException: Server returned HTTP response code:
503 for URL: http://ws.geonames.org/search?name=Paris&maxRows=5&type=json&style=FULL
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1313)
at org.apache.stanbol.enhancer.engines.geonames.impl.GeonamesAPIWrapper.searchToponyms(GeonamesAPIWrapper.java:358)
at org.apache.stanbol.enhancer.engines.geonames.impl.LocationEnhancementEngine.computeEnhancements(LocationEnhancementEngine.java:292)
... 42 more
I suggest to deactivate all engines that depend on external service
for the integration builds. However I have no Idea how to do that
other than creating an own sling launcher configuration that excludes
such engines.
best
Rupert
On Sat, Feb 12, 2011 at 10:52 PM, Apache Hudson Server
<hu...@hudson.apache.org> wrote:
> See <https://hudson.apache.org/hudson/job/stanbol-trunk-1.6/org.apache.stanbol$org.apache.stanbol.enhancer.integration-tests/15/>
>
>
>
--
| Rupert Westenthaler rupert.westenthaler@gmail.com
| Bodenlehenstraße 11 ++43-699-11108907
| A-5500 Bischofshofen