You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Kirhold (Jira)" <ji...@apache.org> on 2020/06/16 18:30:00 UTC

[jira] [Commented] (NIFI-4315) Upgrade to newer version of logback

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

Kirhold commented on NIFI-4315:
-------------------------------

Version of logback is still not upgrade, and we has issue with rolling policy - logger is creating .tmp files:

[https://stackoverflow.com/questions/57356319/spring-boot-logback-xml-creating-tmp-files]

 

This is fixed in 1.3.0 which is in alpha since.. January 18th, 2018. I upvoted that Jira, we should forget about it in future.

> Upgrade to newer version of logback
> -----------------------------------
>
>                 Key: NIFI-4315
>                 URL: https://issues.apache.org/jira/browse/NIFI-4315
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>    Affects Versions: 1.3.0
>            Reporter: Aldrin Piri
>            Priority: Major
>
> There are some bugs outstanding with logback that can cause compression to fail in some environments (was able to recreate in Windows and OS X), seemingly related to the current outstanding issue: https://jira.qos.ch/browse/LOGBACK-1162
> This will also cause the given set of files to grow beyond their bounds of a specified totalSizeCap if one is provided.
> Steps I used to create this comprised:
> * Using a simple flow that generates flow files and terminates them at an update attribute is sufficient.
> * Adjust logback to have DEBUG level for the root logger.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)