[
https://issues.apache.org/jira/browse/NIFI-4315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17899831#comment-17899831
]
Daniel Stieglitz commented on NIFI-4315:
----------------------------------------
[~Kirhold] [~exceptionfactory] [~joewitt] We are having the same issue on our
system with the tmp files of the nifi-bootstrap log. Based on my reading of the
fix for [LOGBACK-1162|https://jira.qos.ch/browse/LOGBACK-1162] and the
corresponding
[documentation|https://logback.qos.ch/manual/configuration.html#stopContext] it
would seem that upgrading the version is not enough. It would be necessary to
add the following tag
{code:java}
<shutdownHook/>{code}
in the logback.xml file configuration. Is that something we can add?
> 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.20.10#820010)
