[
https://issues.apache.org/jira/browse/NIFI-8461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17333202#comment-17333202
]
Francois Liot commented on NIFI-8461:
-------------------------------------
I got the very same issue, using Python scripting,
*It seems as soon as I change the python script, the flows are never treated
anymore, without reporting anything.*
!image-2021-04-27-14-23-24-477.png!
Fully restarting Nifi makes the change of the python script taken into account,
and flows treated normally,
But, if I change again the python script, he flows are never treated anymore,
without reporting anything....
_*Note:* I'm a long time Nifi user, and I hereby declare that this issue
appears between 1.11.4 (where changing script with a simple stop/edit/start
processor, was perfectly working) and 1.13.2 version (where after changing
python script content, the flows won't be treated until full restart)._
As proposed by [~markap14], I tried to get
[http://localhost:8080/nifi-api/processors/1330e49e-0179-1000-21a5-6faa2a2aaddf/diagnostics|http://localhost:8080/nifi-api/processors/1330e49e-0179-1000-21a5-6faa2a2aaddf/diagnostics,],
and also the same with https/8443, but maybe because of my SAML configuration,
the only answer I have is "_Anonymous authentication has not been configured._"
> Queue reports items but cannot list them
> ----------------------------------------
>
> Key: NIFI-8461
> URL: https://issues.apache.org/jira/browse/NIFI-8461
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.13.2
> Environment: Docker image apache/nifi :1.13.2, Windows 10 Pro, WSL 2
> (Ubuntu), x86_64
> Reporter: Kevin Aagaard
> Priority: Major
> Labels: queue
> Attachments: image-2021-04-22-08-48-58-117.png,
> image-2021-04-22-08-49-40-904.png, image-2021-04-27-14-23-07-849.png,
> image-2021-04-27-14-23-24-477.png
>
>
> The following segment of workflow demonstrates the issue. The queue reports
> that there are items within it, but they cannot be listed, even after
> stopping the consumer (and producer). Since this is in a Docker Container, it
> is unlikely an OS error.
>
> !image-2021-04-22-08-48-58-117.png!
>
> !image-2021-04-22-08-49-40-904.png!
> I do not currently have a simplified example workflow to recreate the error,
> but can work on it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
