Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 95374200C15 for ; Wed, 25 Jan 2017 02:35:57 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 93C6A160B4B; Wed, 25 Jan 2017 01:35:57 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 93482160B3E for ; Wed, 25 Jan 2017 02:35:56 +0100 (CET) Received: (qmail 96427 invoked by uid 500); 25 Jan 2017 01:35:55 -0000 Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Developers List" Reply-To: "Log4J Developers List" Delivered-To: mailing list log4j-dev@logging.apache.org Received: (qmail 96417 invoked by uid 99); 25 Jan 2017 01:35:55 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Jan 2017 01:35:55 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 4BEFC180688 for ; Wed, 25 Jan 2017 01:35:55 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.3 X-Spam-Level: * X-Spam-Status: No, score=1.3 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id Gnjs3KPKTKC8 for ; Wed, 25 Jan 2017 01:35:53 +0000 (UTC) Received: from smtp618.redcondor.net (smtp618.redcondor.net [208.80.206.18]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 9205A5F47F for ; Wed, 25 Jan 2017 01:35:52 +0000 (UTC) Received: from mailproxy12.neonova.net ([137.118.22.77]) by smtp618.redcondor.net ({25934d7d-0c4d-4838-a484-2a3cc0768185}) via TCP (outbound) with ESMTP id 20170125013541417_0618 for ; Wed, 25 Jan 2017 01:35:41 +0000 X-RC-FROM: X-RC-RCPT: Received: from [192.168.1.14] (ip72-201-73-113.ph.ph.cox.net [72.201.73.113]) (Authenticated sender: ralph.goers@dslextreme.com) by mailproxy12.neonova.net (Postfix) with ESMTPA id ECD993600D7 for ; Tue, 24 Jan 2017 20:35:37 -0500 (EST) From: Apache Content-Type: multipart/alternative; boundary="Apple-Mail=_0329A79D-E5D9-41C7-B544-DBB68078D50B" Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: RollingAppenderSizeTest Date: Tue, 24 Jan 2017 18:35:37 -0700 References: <1DDCF831-580D-4A7B-A150-4B25F5D9B458@dslextreme.com> To: Log4J Developers List In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.3259) X-DLP-OUTBOUND: 137.118.22.64/27 X-MAG-OUTBOUND: greymail.redcondor.net@137.118.22.64/27 archived-at: Wed, 25 Jan 2017 01:35:57 -0000 --Apple-Mail=_0329A79D-E5D9-41C7-B544-DBB68078D50B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 That is in 2.8. Just don=E2=80=99t specify a file name. The only = downside is that when the system is shut down the file isn=E2=80=99t = compressed. That is because it will be reused if you immediately = restart. But if it no longer matches the file pattern it will never be = compressed. Of course, if you don=E2=80=99t compress the files you will = never have this problem. FWIW, the RollingFileAppender in Log4j 1.x and Logback have always been = the most problematic components just by the nature of what they are = trying to do and how they work. Ralph > On Jan 24, 2017, at 3:24 PM, Gary Gregory = wrote: >=20 > It feels like we've had so many issues with the rolling file appender = for so long. For me, I'd rather have a "rolling" file appender be more = like a "time window" file appender where NO files are renamed. For = example, with a time window/rollover of 1 day you start with a file = called 2017-01-01.txt and on "rollover", we start a new file = 2017-01-02.txt. The "rolling" is that we "roll" logging to the new file. = The old file can still be compressed like before. And old old files can = still be deleted based on the file pattern. >=20 > When I first started using the RFA, I was surprised at the behavior = for always writing to the same file name and then copying that on = rollover. Diff'rent strokes I guess ;-) >=20 > Gary >=20 > On Tue, Jan 24, 2017 at 12:03 PM, Apache > wrote: > I am looking at the failures that are occurring in the = RollingAppenderSizeTest in the Jenkins build. I am working at modifying = the code so that the asynchronous tasks will complete before shutdown is = allowed to complete. But I am running into an issue I am not sure how to = resolve. The test is configured to have the log file roll over after 500 = bytes have been written. It seems that some of the compression = algorithms take longer than it takes to write 500 bytes, so after the = maximum number of files are reached the system is rolling over on top of = files that are in the process of being archived, so we get rename/move = and delete problems. >=20 > Any ideas? >=20 > Ralph >=20 > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org = > For additional commands, e-mail: log4j-dev-help@logging.apache.org = >=20 >=20 >=20 >=20 > --=20 > E-Mail: garydgregory@gmail.com | = ggregory@apache.org > Java Persistence with Hibernate, Second Edition = =C2=A0 = > JUnit in Action, Second Edition = =C2=A0 = > Spring Batch in Action = = > Blog: http://garygregory.wordpress.com = =20 > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory --Apple-Mail=_0329A79D-E5D9-41C7-B544-DBB68078D50B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8
That is in 2.8. Just don=E2=80=99t specify a = file name. The only downside is that when the system is shut down the = file isn=E2=80=99t compressed. That is because it will be reused if you = immediately restart. But if it no longer matches the file pattern it = will never be compressed. Of course, if you don=E2=80=99t compress the = files you will never have this problem.

FWIW, the RollingFileAppender in Log4j = 1.x and Logback have always been the most problematic components just by = the nature of what they are trying to do and how they work.

Ralph

On = Jan 24, 2017, at 3:24 PM, Gary Gregory <garydgregory@gmail.com> wrote:

It feels like we've had so many issues with the rolling file = appender for so long. For me, I'd rather have a "rolling" file appender = be more like a "time window" file appender where NO files are renamed. = For example, with a time window/rollover of 1 day you start with a file = called 2017-01-01.txt and on "rollover", we start a new file = 2017-01-02.txt. The "rolling" is that we "roll" logging to the new file. = The old file can still be compressed like before. And old old files can = still be deleted based on the file pattern.

When I first started using the RFA, I = was surprised at the behavior for always writing to the same file name = and then copying that on rollover. Diff'rent strokes I guess ;-)

Gary

On Tue, Jan 24, 2017 at 12:03 PM, = Apache <ralph.goers@dslextreme.com> wrote:
I am looking at the = failures that are occurring in the RollingAppenderSizeTest in the = Jenkins build. I am working at modifying the code so that the = asynchronous tasks will complete before shutdown is allowed to complete. = But I am running into an issue I am not sure how to resolve. The test is = configured to have the log file roll over after 500 bytes have been = written. It seems that some of the compression algorithms take longer = than it takes to write 500 bytes, so after the maximum number of files = are reached the system is rolling over on top of files that are in the = process of being archived, so we get rename/move and delete problems.

Any ideas?

Ralph

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




--
E-Mail:= garydgregory@gmail.com | ggregory@apache.org
Java Persistence with = Hibernate, Second Edition 
JUnit in Action, Second = Edition 
Spring Batch in Action
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

= --Apple-Mail=_0329A79D-E5D9-41C7-B544-DBB68078D50B--