[jira] [Commented] (LOG4J2-3135) When the application logs cross the specified roll back limit, the next logs getting created does not carry the same name as the zip file name created.

["Ralph Goers (Jira)" <ji...@apache.org>]

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

Ralph Goers commented on LOG4J2-3135:
-------------------------------------

There is not enough information here. We would need a sample configuration at the very least. A directory listing would also be helpful.

> When the application logs cross the specified roll back limit, the next logs getting created does not carry the same name as the zip file name created.
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: LOG4J2-3135
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-3135
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Appenders
>    Affects Versions: 2.13.3
>         Environment: Production, UAT, and Development
>            Reporter: Kratika Shah
>            Priority: Major
>
> Open file log4j2.xml in the notepad or any editor. In the Configuration section, in the file Application configuration folder\log4j2.xml, change the Number of Files as below: -
> In the same file, Go to <Properties> tag and add a line: <Property name="NumberOfFiles">20</Property> You can keep the default values as well.
> When the application logs cross the specified limit, the naming convention of the logs is not as expected.
> Example: The zip file gets created with the name App-2020-Jul-28-1.log and when we extract the log, the file name would be App-2020-Jul-28-28.log



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