On T= ue, Jul 23, 2013 at 6:17 PM, Remko Popma <remkop@yahoo.com> w= rote:

Understood about Came= lCase, not a problem.

Maybe AsyncLoggers is a better element name anyway. How does this look= ?

<configuration level=3D"warn"=C2= =A0Log4jContextSelector=3D"org.apache.logging.log4j.core.async.= AsyncLoggerContextSelector">
=C2=A0 <AsyncLogger= s exceptionHandler=3D"my.custom.Handler"=C2=A0ringBufferSize=3D&q= uot;128" waitStrategy=3D"Block" />

=C2=A0 <jmx enabled=3D"true" />
</configuration>
Sorry, I don't remember what email from Simo y= ou are referring to.

Please read https://mail-archives.apache.org/mod_mbox/logging-log4j-dev/201306.mbox/%3= CCAAqLGLNpLiZRP_8SJXcttYutVHJFNuqNxvr3HruaLpKaG12FvA@mail.gmail.com%3E<= br>

Gary
=C2=A0

From: Gary Gregory <garydgregory@gmail.com>

To: Log4J Developers Li= st <lo= g4j-dev@logging.apache.org>

Sent: Wednesday, July 24, 2013 7:07 AM

Subject:<= /b> Re: Config additions, WAS: Confused: want low latency: do I need BOTH async logger AND async appender??

What is up with the dashes in element= names? That is unsightly IMO. I know that we have some - IMO unnecessary = =C2=A0- flexibility in our config code to make XML case insensitive but das= hes we have in there now make it impossible to make the XML look decent. If= it were just me I would use CamelCase for element names (like class names)= and camelCase for attribute names (like instance variable names).=C2=A0

Simo has emailed about a different approach to configur= ation. Does anyone have comments on that btw? I know, I should start a diff= erent thread...

Gary

On Jul 23, 2013, at 17:57, Remko = Popma <remkop@yahoo.com> wrote:

After looking at your changes for=C2= =A0LOG4J2-318=C2=A0to add the shutdownHookEnabled = attribute I understand a bit better.

=
Here is a list of properti= es that can be used to configure AsyncLoggers when all loggers are Async:
* Log4jContextSelector=3Dorg.apache.logging.log4j.core.async.AsyncLoggerCont= extSelector
* AsyncLogger.E= xceptionHandler
* AsyncLogg= er.RingBufferSize

* AsyncLogger.WaitStrategy
=
* log4j.Clock - currently only used for= timestamping RingBufferLogEvents. Should all LogEvents=C2=A0
<= div style=3D"font-size:10pt">
The following system p= roperties can be used to configure mixed Async Loggers:

= * AsyncLoggerConfig.ExceptionHandler <= /span>
* AsyncLoggerConfig.RingBufferSize
* AsyncLoggerConfig.WaitStrategy

For JMX there is only the on= e "disable" property, which Gary suggested to make into an elemen= t rather than an attribute to future-proof it.

<= br>
So, should the result look something like th= is?

<configuration level=3D&q= uot;warn"=C2=A0Log= 4jContextSelector=3D"org.apache.logging.log4j.core.async.AsyncLoggerCo= ntextSelector">

=C2=A0 <async-configuration exceptionHandler=3D"my.custom.Handler"=C2=A0ringBufferSize=3D"128" waitStrategy=3D&q= uot;Block" />
</configuration>

From: Ralph Goers <= ralph.goers@dslextreme.com>
To: Log4J Developers List &= lt;log4j-dev@logging.apache.org>
Sent: Wednesday, July 24, 2013 2:38 AM
Subject: Re: Config additio= ns, WAS: Confused: want low latency: do I need BOTH async logger AND async = appender??

What don't you know?=C2=A0 I'= ;d be happy to help with that :-)

Ralph

On Jul 23, 2013, at 9:20 AM, Remko Popma wrote:
> I wouldn't mind doing this but don't know how.
>
> Remko
>
> Sent from my iPhone
> =
> On 2013/07/24, at 0:46, Nick Williams <nicholas@nichol= aswilliams.net> wrote:
>
>> I don't know the answer to this guy's question on= the user's list, but it brought up something interesting that we need = to look at. Already (in a separate issue) we have talked about needing a co= nfig element for JMX so that you don't have to use properties in this m= anner. IMO, if there's not a way to set these AsyncLogger configuration= options in log4j2.xml/json, that needs to be added, too. You should never = have to do System.setProperty (or -D on the command line) to get Log4j conf= igured properly.
>>
>> My $0.02.
>>
>> Nick
>> <= br>>> On Jul 23, 2013, at 10:39 AM, SMITH, CURTIS wrote:
>> =
>>> http://logging.apache.org/log4j/= 2.x/manual/async.html
>>>
>>> This URL describes that v2 has both async log= ger and async appender.=C2=A0 What is the suggested config for an embedded= situation where I want low latency, nothing fancy?
>>>
>= ;>> I've had do this in code since we don't own the cmd line:= =C2=A0 OSGi and system vendor owns the box and java command line.
>>>
>>> System.setProperty("AsyncLoggerContextSe= lector", "org.apache.logging.log4j.core.async.AsyncLoggerContextS= elector");
>>> System.setProperty("AsyncLogger.RingBu= fferSize", "128");=C2=A0 =C2=A0 =C2=A0 =C2=A0 // min size pe= rmissable to keep memory low
>>> System.setProperty("AsyncLogger.WaitStrategy", "= ;Block");=C2=A0 =C2=A0 =C2=A0 =C2=A0 // less CPU, better for embedded = env
>>> System.setProperty("log4j2.disable.jmx", "true");=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 // saves on a jmx jar and we= don't use JMX anyway
>>>
>>> Tnx curt
>= >>
>>> Curt Smith
>>> AT&T Digital Life
>>> DLC Software Development=
>>> 404-499-7013
>>> (cell) 678-365-6508
>&g= t;
>>
>> ----------------------------------------------= -----------------------
>> To unsubscribe, e-mail: log4j-dev-unsubscribe@= logging.apache.org
>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>
>
> ---------------------------------------------------------------------
&= gt; To unsubscribe, e-mail: log4j-dev-unsubscribe@loggi= ng.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.a= pache.org
>

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

=

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