[MAGNOLIA-6881] Switch to log4j2 Created: 22/Nov/16 Updated: 08/Sep/17 Resolved: 08/Sep/17 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Torsten Landmann | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
Magnolia still uses log4j although it has a severe performance bug in org.apache.log4j.Category:204 (method callAppenders()), namely the synchronized block there. A natural improvement would be the switch to log4j2, which is already available in version 2.7. There is also a bridge available which allows you to use the conventional log4j code to create loggers (so you don't need to adapt each of cour classes before you can switch to log4j2). |
| Comments |
| Comment by Mikaël Geljić [ 08/Sep/17 ] |
|
Hi Torsten, thanks for reporting Actually, we already have this item as I'll therefore close this ticket as duplicate. Cheers, |