Mailing-List: contact log4j-user-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Users List" <log4j-user@logging.apache.org>
From: Remko Popma <remko.popma@gmail.com>
Content-Type: text/plain;
	charset=shift_jis
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Date: Thu, 17 Nov 2016 08:36:24 +0900
Subject: Re: [log4j 1.x] Batch-sending with SMTPAppender
Message-Id: <756CE4D2-A854-43BE-8A3B-20D14DEAA44B@gmail.com>
References: <e8aba82f-e04f-d965-583e-86acaaa7659c@christopherschultz.net> <B3B9AFED-5712-4654-B189-CD55F7EE8BBC@dslextreme.com> <51df962f-3c7c-d4ba-2f12-b96553a2211f@christopherschultz.net> <1F899ABE-8115-45DF-98B8-3CBCD0853D83@dslextreme.com> <alpine.WNT.2.11.1611161339440.9088@seil> <39a3e6d1-dcc2-2da7-8bc9-8c014781834c@christopherschultz.net>
In-Reply-To: <39a3e6d1-dcc2-2da7-8bc9-8c014781834c@christopherschultz.net>
To: Log4J Users List <log4j-user@logging.apache.org>
archived-at: Wed, 16 Nov 2016 23:36:38 -0000

Chris,

Are you aware that there is a log4j-1.2-api adapter included in Log4j2 that a=
llows you to keep your application code unchanged (unless you rely on the in=
nards of Log4j 1.2)?

You only need to change the configuration (the manual has tons of examples).=
=20

Just FYI.=20
Remko

Sent from my iPhone

> On 17 Nov 2016, at 7:33, Christopher Schultz <chris@christopherschultz.net=
> wrote:
>=20
> Scott,
>=20
> On 11/16/16 2:09 PM, Scott Harrington wrote:
>>>>> On 11/16/16 9:49 AM, Ralph Goers wrote:
>>>>> First, I have to say that Log4j 1 reached end-of-life over a year
>>>>> ago. We recommend you upgrade to Log4j 2.
>>>>=20
>>>> Fair enough. I'm not quite there, yet. I suspect that log4j 2 will have=

>>>> the same issue, though.
>>>=20
>>> I don=81ft know how to configure a TriggeringEventEvaluator in Log4j 1
>>> but I=81fd bet google does ;-)
>>=20
>> Chris: I have a ThrottledSMTPApppender subclass that I used for years
>> under Log4j 1.x, it's very small but was somewhat tricky; it starts a
>> "flusher" thread and attaches a shutdown hook to drain before exit.
>> There is a TriggeringEventEvaluator that always returns false. There is
>> a configureable "initialDelay" (default 10 seconds) and
>> "messageInterval" (default 60 seconds).
>=20
> That sounds cool, but maybe overkill if I can get the
> TriggeringEventEvaluator working with the stock log4j distro.
>=20
> (It looks like I'll need to write my own NeverTriggerEventEvaluator to
> do that. It looks trivial so I'll try that first.)
>=20
>> I've since moved up to Log4j 2, and you are correct that Log4j 2 didn't
>> do throttling/batching quite like I wanted, so I have a "ThrottledSMTP"
>> Plugin for Log4j 2.
>=20
> :)
>=20
>> There was some discussion of this at LOG4J2-252, which is still open.
>> I'll attach my two variants to that ticket with the hope they may be
>> useful as-is to you or to others. However I don't have the time in
>> foreseeable future to prepare the proper unit test and documentation
>> that would be required to make it part of official Log4j2.
>=20
> Understood. If I (a) go down the ThrottledSMTPAppender route and (b)
> move to log4j 2, I may finish-off that work. It's a long-shot, though.
>=20
> I really appreciate the feedback, though.
>=20
> -chris
>=20

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