Uploaded image for project: 'Apache NiFi'
  1. Apache NiFi
  2. NIFI-3616

Flushing and listing queues becomes unavailable when running clusters



    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Not A Problem
    • Affects Version/s: 1.2.0, 1.1.1
    • Fix Version/s: None
    • Component/s: Core UI
    • Environment:
      OS: Ubuntu 16.04.2, 4.4.0-66-generic
      Java: 1.8.0_121 (openjdk-8-jre-headless)

      Issue confirmed on both physical and virtual platforms.


      When setting up a new cluster with NiFi 1.1.2 (which is not available under "Affect version/s"), it is not possible to flush or list queues in connections.

      See attached screenshots for error message.

      Procedure for reproducing:
      1) Set up a new cluster with i.e. 3 nodes
      2) Grant yourself necessary policies for the root process group[0].
      3) Create two funnels
      4) Create a connection between those funnels
      5) Right click on the connection and choose "List queue". This produces the error message "Unable to perform the desired action due to insufficient permissions. Contact the system administrator.". The same thing will happen if you try to empty the queue (even when empty).

      In my test setup I currently have some flowfiles in one of the connections, and have yet to find a workaround allowing me to empty it.

      The following error message is produced in nifi-app.log on all nodes:

      2017-03-16 13:37:03,141 INFO [NiFi Web Server-509] o.a.n.w.a.c.AccessDeniedExceptionMapper EMAILADDRESS=XXX, CN=XXX, C=XX does not have permission to access the requested resource. Returning Forbidden response.

      Starting a single node instance repeating the exact steps above does not produce this error.

      Please let me know if further information or files are needed.

      [0]: "View the component", "Modify the component", "View the data", "Modify the data".




            • Assignee:
              frsk Fredrik Skolmli
            • Votes:
              0 Vote for this issue
              1 Start watching this issue


              • Created: