You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@nifi.apache.org by "Matt Gilman (JIRA)" <ji...@apache.org> on 2015/06/23 22:16:42 UTC

[jira] [Updated] (NIFI-683) When connecting to cluster, splash screen remains indefinitely if error sent back

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

Matt Gilman updated NIFI-683:
-----------------------------
    Attachment: 0001-NIFI-683.patch

> When connecting to cluster, splash screen remains indefinitely if error sent back
> ---------------------------------------------------------------------------------
>
>                 Key: NIFI-683
>                 URL: https://issues.apache.org/jira/browse/NIFI-683
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core UI
>            Reporter: Mark Payne
>             Fix For: 0.2.0
>
>         Attachments: 0001-NIFI-683.patch
>
>
> I created a cluster with the NCM running on my host and a single node running in a VM. In the VM, I configured the node to report its fully qualified hostname. The Host running the NCM, however, does not recognize the fully qualified hostname of the VM and gets a Socket Read timeout. This is returned to the UI as a 409: Conflict.
> The UI ignores this, leaving the splash screen. The UI should instead report back an error, as it does if there are no connected nodes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)