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

Posted to dev@apex.apache.org by "Vlad Rozov (JIRA)" <ji...@apache.org> on 2017/03/03 16:45:45 UTC

[jira] [Resolved] (APEXCORE-563) Have a pointer to container log file name and offset in stram events that deliver a container or operator failure event.

     [ https://issues.apache.org/jira/browse/APEXCORE-563?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vlad Rozov resolved APEXCORE-563.
---------------------------------
       Resolution: Implemented
    Fix Version/s: 3.6.0

> Have a pointer to container log file name and offset in stram events that deliver a container or operator failure event.
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: APEXCORE-563
>                 URL: https://issues.apache.org/jira/browse/APEXCORE-563
>             Project: Apache Apex Core
>          Issue Type: New Feature
>            Reporter: Sanjay M Pujare
>            Assignee: Priyanka Gugale
>             Fix For: 3.6.0
>
>
> The default DailyRollingFileAppender does not take into account of how many backup files to keep and it will result in unbounded growth of log files, especially for long running applications.
> The below is an interesting add-on to the default DailyRollingFileAppender that supports maxBackupIndex.
> http://wiki.apache.org/logging-log4j/DailyRollingFileAppender



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)