You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jim Challenger (JIRA)" <de...@uima.apache.org> on 2014/07/21 18:34:39 UTC

[jira] [Closed] (UIMA-3899) DUCC CLI Long pauses for all CLI operations

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

Jim Challenger closed UIMA-3899.
--------------------------------

    Resolution: Fixed

> DUCC CLI Long pauses for all CLI operations
> -------------------------------------------
>
>                 Key: UIMA-3899
>                 URL: https://issues.apache.org/jira/browse/UIMA-3899
>             Project: UIMA
>          Issue Type: Improvement
>          Components: DUCC
>    Affects Versions: 1.0.0-Ducc
>            Reporter: Jim Challenger
>            Assignee: Jim Challenger
>             Fix For: 1.1.0-Ducc
>
>
> The DUCC CLI currently constructs a new NodeIdentity object as part of initialization.  The NodeIdentity iterates all network interfaces trying to find all the ways "me" is identified.  The CLI then uses only the "getIp()" method which returns exactly the results from InetAddress.getLocalHost().getHostAddress();.
> The problem is that iterating all those interfaces can take a long time and if there is a mis-configured or otherwas errant NIC the pause can be significant, on the order of minutes.
> This JIRA is to track changing the CLI to use InetAddress.getLocalHost().getHostAddress(); directly instead of NodeIdentity for this purpose.  Initial testing indicates a significant improvement in interactive response.



--
This message was sent by Atlassian JIRA
(v6.2#6252)