You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org> on 2017/07/14 13:39:00 UTC

[jira] [Closed] (UIMA-5469) UIMA-DUCC: The JP code not handling HttpHostConnectException

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

Jerry Cwiklik closed UIMA-5469.
-------------------------------
    Resolution: Fixed

Modified to improve recovery from lost connection to a remote JD/Task Allocator

> UIMA-DUCC: The JP code not handling HttpHostConnectException 
> -------------------------------------------------------------
>
>                 Key: UIMA-5469
>                 URL: https://issues.apache.org/jira/browse/UIMA-5469
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Jerry Cwiklik
>            Assignee: Jerry Cwiklik
>             Fix For: 2.2.1-Ducc
>
>
> Error handling for HttpHostConnectionException is incomplete. When the HttpClient looses connection to the JD's Web Server, the above exception is thrown. There is an explicit 
>  catch() to deal with it but all it does now is just log the problem once. So what happens in this scenario is that a thread fails over and over again. 
> What should happen here is that a single thread should attempt connection recovery sleeping for awhile (default=60sec) and try again. Other threads (if scaleout > 1), should block doing nothing until a thread doing the retry succeeds.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)