- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Could not find port with name 'portName' for remote NiFi instance
- Labels:
-
Apache NiFi
-
Apache Storm
Created ‎07-06-2016 03:36 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, I cannot connect my NifiStorm java class to my NiFi instance. I get an exception error "Could not find port with name portName for remote NiFi instance". My NiFi instance is running with the port name = "portName" and Ambari reports that the DRPC server, nimbus, and the UI Server has started. It also reports that the Supervisor is live. I have Storm on my sandbox - HDP 3.2. What could be causing this unrecognized port name error?
Created ‎07-06-2016 06:37 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I did not know about the secure mode option. I set the secure mode to false in the properties file and it fixed the issue. Thanks!
Created ‎07-06-2016 04:02 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is the port that you create in NiFi an Output Port on the root group? If not, you will need to make sure that you have it configured this way. Also, if you are running NiFi in secure mode, you will need to ensure that your client authenticates properly and that you have granted access to client in NiFi by configuring the port and going to the 'Access Controls' tab.
Created ‎07-06-2016 04:03 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Could provide a screen shot of your NiFi flow showing the output port?
Created ‎07-06-2016 06:37 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I did not know about the secure mode option. I set the secure mode to false in the properties file and it fixed the issue. Thanks!
