[
https://issues.apache.org/jira/browse/NIFI-683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14599385#comment-14599385
]
ASF subversion and git services commented on NIFI-683:
------------------------------------------------------
Commit 3a05a7da721d70767ab3ad9a6827a10e2d318725 in incubator-nifi's branch
refs/heads/develop from [~mcgilman]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=3a05a7d ]
NIFI-683:
- Add explicit handling of errors that occur during the initial page loading.
> 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
> Assignee: Matt Gilman
> Fix For: 0.2.0
>
> Attachments: 0001-NIFI-683.patch, 0002-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)
