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 2013/06/24 11:50:21 UTC

[jira] [Updated] (STANBOL-1118) Namespace Prefix Provider prefixcc Build fail when the prefixcc service is not available

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

Rupert Westenthaler updated STANBOL-1118:
-----------------------------------------

    Attachment: STANBOL-1118_20130624_rw.patch

Attached a patch that:

* changes the provider to create a Url Connection on each request
* sets also a connection/read timeout of 5sec
* closes the InputStream
* disconnects http (as this provider will send the next request only after a long period)

Also added a similar check to the unit test - to prevent errors in the test if the service is down.

NOTE: I was not able to test if the error handling correctly detects and handles outages of the service as encountered last week, as the service is in the meantime up and running.

                
> Namespace Prefix Provider prefixcc Build fail when the prefixcc service is not available
> ----------------------------------------------------------------------------------------
>
>                 Key: STANBOL-1118
>                 URL: https://issues.apache.org/jira/browse/STANBOL-1118
>             Project: Stanbol
>          Issue Type: Bug
>          Components: Commons
>    Affects Versions: commons-0.11.0
>            Reporter: Rafa Haro
>         Attachments: STANBOL-1118_20130624_rw.patch
>
>
> PrefixccProvider is expecting a text/plain and Status 200 response with Namespace prefixes from http://prefix.cc/popular/all.file.txt. When the service is not available, Content-type response is text/html and the content is an error message that prevents module building due to test cases failure.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira