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

Bohdan Mushkevych updated LOG4J2-550:
-------------------------------------

    Description: 
I am using log4j 2.0-rc1, StructuredDataMessage and EventLogger to perform 
dynamic logging.

Attached log4j2.xml configuration meant to:
- rotate log files on hourly basis OR after file reaches 64 MB (whatever comes 
first)
- archive logs that does not satisfy the file pattern

Whenever JVM is restarted, log4j abandons "old" files un-archived:

-rw-r--r--. 1 root root   317625 Feb 24 20:16 
2014022419-sim-mdmlocal.mobidia.com.log
-rw-r--r--. 1 root root  3333648 Feb 24 20:20 
2014022420-activity-mdmlocal.mobidia.com.log

Listing above shows that file 2014022419-sim-mdmlocal.mobidia.com.log was last 
touched by the system at 20:16, and should have been archived to .log.gz after 
restart, which occurred soon after

  was:
I am using log4j 2.0-rc1, StructuredDataMessage and EventLogger to perform 
dynamic logging.

Attached log4j2.xml configuration meant to:
- rotate log files on hourly basis OR after file reaches 64 MB (whatever comes 
first)
- archive logs that does not satisfy the file pattern

Whenever JVM is restarted, log4j abandons "old" files un-archived:

-rw-r--r--. 1 root root   317625 Feb 24 20:16 
2014022419-sim-mdmlocal.mobidia.com.log
-rw-r--r--. 1 root root  3333648 Feb 24 20:20 
2014022420-activity-mdmlocal.mobidia.com.log



> .log files are left un-archived after JVM restart
> -------------------------------------------------
>
>                 Key: LOG4J2-550
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-550
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0-rc1
>            Reporter: Bohdan Mushkevych
>         Attachments: log4j2.xml
>
>
> I am using log4j 2.0-rc1, StructuredDataMessage and EventLogger to perform 
> dynamic logging.
> Attached log4j2.xml configuration meant to:
> - rotate log files on hourly basis OR after file reaches 64 MB (whatever 
> comes first)
> - archive logs that does not satisfy the file pattern
> Whenever JVM is restarted, log4j abandons "old" files un-archived:
> -rw-r--r--. 1 root root   317625 Feb 24 20:16 
> 2014022419-sim-mdmlocal.mobidia.com.log
> -rw-r--r--. 1 root root  3333648 Feb 24 20:20 
> 2014022420-activity-mdmlocal.mobidia.com.log
> Listing above shows that file 2014022419-sim-mdmlocal.mobidia.com.log was 
> last touched by the system at 20:16, and should have been archived to .log.gz 
> after restart, which occurred soon after



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Reply via email to