[ 
https://issues.apache.org/jira/browse/NIFI-2304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15398542#comment-15398542
 ] 

ASF GitHub Bot commented on NIFI-2304:
--------------------------------------

Github user ijokarumawak commented on the issue:

    https://github.com/apache/nifi/pull/688
  
    @markap14 Thanks for the updates!
    I tested the latest PR, set `nifi.cluster.node.address` as blank in 
nifi.properties, confirmed that e node NiFi cluster can start up successfully.
    
    However, for `nifi.cluster.node.protocol.port`, there's another usage of 
that configuration, and I got following error message with blank property value:
    
    ```
    Caused by: 
org.springframework.beans.factory.UnsatisfiedDependencyException: Error 
creating bean with name 'protocolListener' defined in class path resource 
[nifi-cluster-protocol-context.xml]: Unsatisfied dependency expressed through 
constructor argument with index 1 of type [int]: Could not convert constructor 
argument value of type [null] to required type [int]: Failed to convert value 
of type [null] to required type [int]; nested exception is 
java.lang.IllegalArgumentException: Cannot convert value of type [null] to 
required type [int]: PropertyEditor 
[org.springframework.beans.propertyeditors.CustomNumberEditor] returned 
inappropriate value of type [null]
            at 
org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:724)
 ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
            at 
org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:185)
 ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
            at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1143)
 ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
            at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1046)
 ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
            at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:510)
 ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
            at 
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482)
 ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
            at 
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
 ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
            at 
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
 ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
            at 
org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
 ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
            at 
org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
 ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
            at 
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:351)
 ~[spring-beans-4.2.4.RELEASE.jar:4.2.4.RELEASE]
            ... 52 common frames omitted
    ```


> Cluster Coordinator reported incorrectly
> ----------------------------------------
>
>                 Key: NIFI-2304
>                 URL: https://issues.apache.org/jira/browse/NIFI-2304
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>            Reporter: Bryan Bende
>            Assignee: Mark Payne
>            Priority: Minor
>             Fix For: 1.0.0
>
>
> I created a two node cluster locally, running embedded ZK on node1.. both 
> nodes start up, but when trying to access the UI on the second node, it says 
> no coordinator exists. 
> Looking in the logs the coordinator is being reported as ":8889" where 8889 
> is the node protocol port. I left the node host blank assuming it would 
> default to localhost, but looks like it isn't. When I filled in the node host 
> everything worked as expected.



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

Reply via email to