[ https://issues.apache.org/jira/browse/SLING-4875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chetan Mehrotra resolved SLING-4875. ------------------------------------ Resolution: Duplicate [~petitbear68] I think this issue is duplicate of SLING-4788 logged earlier by you. For now I am closing this. Let me know if you think its a different issue > Enhance the SlingConfigurationPrinter for better handling of large logs > ----------------------------------------------------------------------- > > Key: SLING-4875 > URL: https://issues.apache.org/jira/browse/SLING-4875 > Project: Sling > Issue Type: Improvement > Components: Commons > Affects Versions: Commons Log 4.0.2 > Reporter: Thierry Ygé > > Currently it often happen that the configuration status zip fail to create > (truncated zip is generated). > Most of the time it is due to large logs being added in the status. > There already the problem that logs are added "twice", once as txt in the > zip, and once as attachments, the first one must be the cause of the issues. > It would help to: > 1. only add the logs as attachment > 2. remove the "txt" version of the printed logs combined in one super large > file > 3. define a filter so that only recent logs are included and that any old > rotation are skipped (large logs could be scanned to tail only the recent > part like 1 day old , 2 day etc.. as configurable setting). > The class is located here: > http://svn.apache.org/viewvc/sling/trunk/bundles/commons/log/src/main/java/org/apache/sling/commons/log/logback/internal/SlingConfigurationPrinter.java?revision=1670022&view=markup -- This message was sent by Atlassian JIRA (v6.3.4#6332)