I got stuck, and all I can think of are these. Other people may want
to look at this and think about what might compel them to switch to
log4j2 (when we get there.. :) )
Compelling Reasons for a log4j2 adoption
* Ease of migration/Drop in replacement for log4j 1.2 - If we do not
meet this fundamental goal, I seriously doubt we'll ever gain
traction. We should be free from the log4j1.2 design, but we should
begin early to ensure that the core design can be easily shimmed with
a log4j2-1.2compatibility.jar or equivalent.
* Finer grained synchronization - log4j1.2 has a weakness in it's
synchronization mechanism that can cause problems in high load
situations. In it's earlier years this was never a problem, but
more and more people hit these bottlenecks.
* Simplicity of management - 1.2 has a nice and easy .properties
and .xml configuration mechanism but lacks finer grained runtime
management controls. The jmx support in 1.2 is rather weak.
* Advanced Context logging - go beyond MDC and NDC to domains/markers
and other concepts. Provide advanced tools to easily correlate
logging events together for analysis.
* Locale-based logging - not everyone speaks English, or a single
language. Applications written for other countries may wish to
deploy with bundles for logging messages. The var-args support in
Java 5 makes this one easy-peasy. It also can limit the cost of
logging String concatenation and remove the ugly code "if
(LOG.isDebugEnabled())". If the LOG.debug(...) statement can take
var-args, then there is no overhead of string construction until the
actual point you know you have to append something.
* Small core module size - not one big uber jar (people are funny
about large jars) - a somewhat weak argument, but you'd be surprised...
Paul Smith
Core Engineering Manager
Aconex
The easy way to save time and money on your project
696 Bourke Street, Melbourne,
VIC 3000, Australia
Tel: +61 3 9240 0200 Fax: +61 3 9240 0299
Email: [EMAIL PROTECTED] www.aconex.com
This email and any attachments are intended solely for the addressee.
The contents may be privileged, confidential and/or subject to
copyright or other applicable law. No confidentiality or privilege is
lost by an erroneous transmission. If you have received this e-mail
in error, please let us know by reply e-mail and delete or destroy
this mail and all copies. If you are not the intended recipient of
this message you must not disseminate, copy or take any action in
reliance on it. The sender takes no responsibility for the effect of
this message upon the recipient's computer system.
