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

ASF subversion and git services commented on NIFI-14739:
--------------------------------------------------------

Commit 42900ae76cf61c1f1ddb526c27312566e278c3d7 in nifi's branch 
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=42900ae76c ]

NIFI-14739 Added Logback NopStatusListener to Bootstrap Command

- NopStatusListener prevents Logback configuration failures from interfering 
with application run command formatting

Signed-off-by: Pierre Villard <[email protected]>

This closes #10082.


> Add Logback NopStatusListener to Bootstrap Command
> --------------------------------------------------
>
>                 Key: NIFI-14739
>                 URL: https://issues.apache.org/jira/browse/NIFI-14739
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>            Reporter: David Handermann
>            Assignee: David Handermann
>            Priority: Minor
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The NiFi bootstrap process includes Logback initialization that writes 
> configuration messages to the standard output stream when encountering 
> parsing failures. When starting NiFi using the {{run}} command, this 
> additional output interferes with returning the structured application launch 
> command that the launch script uses for running NiFi without the bootstrap 
> monitor process.
> Configuring the Logback NopStatusListener using a Java system property for 
> the NiFi bootstrap process itself avoids interfering with {{run}} command 
> construction. The default behavior of Logback should be retained for the 
> standard Logback configuration as an aid for troubleshooting.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to