I'm seeing odd behavior trying to use attributes for the hostname and port
fields.
using ${endpoint_port} (9003) + hardcoded IP results in flowfile yielding
failed to process session due to java.lang.NumberFormatException: For input
string: "": {}
java.lang.NumberFormatException: For input string: ""
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:592)
at java.lang.Integer.parseInt(Integer.java:615)
at
org.apache.nifi.attribute.expression.language.StandardPropertyValue.asInteger(StandardPropertyValue.java:78)
at org.apache.nifi.processors.standard.PutTCP.createSender
(PutTCP.java:111)
...
at org.apache.nifi.processors.standard.PutTCP.createSender
(PutTCP.java:179)
using hardcoded 9003 + ${endpoint} results in flowfile failing due to
connection refused
DEBUG ...No available connections, creating a new one...
ERROR ...No available connections, and unable to create a new one ....to
failure: java.net.ConnectException: Connection refused
Adding listenTCP to the cluster on 9003 leaving ${endpoint} and hardcoded
port
DEBUG...Connected to local port 23250
DEBUG....Relinquishing sender
Flow files transferred to success, its unclear where the data went or why I
needed to have the nodes listening on this port. Is the attribute value
being ignored and defaulting to localhost? Watching this behavior via
netstat I could see 127.0.0.1 was indeed connected to itself on 9003. Odd
thing is no data came in on the ListenTCP either.
Thanks,
Ryan
