[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14603835#comment-14603835 ] ASF subversion and git services commented on NIFI-683: -- Commit 0df351dcb47432dd0cacf31a2ed5e5765aa96f03 in incubator-nifi's branch refs/heads/NIFI-680 from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=0df351d ] NIFI-683: - Fixing typo. 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)
[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14603776#comment-14603776 ] ASF subversion and git services commented on NIFI-683: -- Commit 0df351dcb47432dd0cacf31a2ed5e5765aa96f03 in incubator-nifi's branch refs/heads/NIFI-632 from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=0df351d ] NIFI-683: - Fixing typo. 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)
[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14599331#comment-14599331 ] Mark Payne commented on NIFI-683: - Matt, Looked at the code. All looks good. Returned the error message, as I expected. Looks like you have a typo in the 'default' error message though: An unexcepted error has occurred That unexcepted should probably have been unexpected :) Otherwise +1 Thanks -Mark 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 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)
[jira] [Commented] (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:comment-tabpanelfocusedCommentId=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)
[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14599386#comment-14599386 ] ASF subversion and git services commented on NIFI-683: -- Commit 0df351dcb47432dd0cacf31a2ed5e5765aa96f03 in incubator-nifi's branch refs/heads/develop from [~mcgilman] [ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=0df351d ] NIFI-683: - Fixing typo. 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)
[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14597694#comment-14597694 ] Mark Payne commented on NIFI-683: - [~mcgilman] I'm not sure which request timed out at this point. I did see in the NCM's logs that it was a SocketTimeoutException that was causing a 409 to be returned. This occurred after I attempted to go to http://localhost:8080/nifi. 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 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)
[jira] [Commented] (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:comment-tabpanelfocusedCommentId=14597517#comment-14597517 ] Matt Gilman commented on NIFI-683: -- [~markap14] You say that the NCM does not recognize the node's hostname, gets a socket read timeout, and returns a 409 to the UI. What REST endpoint was being invoked? Did the 409 response contain any relevant message about the current state? I think I understand the underlying issue on the UI side, with regards to the splash screen situation, but I don't follow the first part of the description. Was it during the connection handshake that it was unable to resolve the hostname? Processing heartbeats? Or during a user request replication? 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 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)
