[MAGNOLIA-4975] Log4j is not working correctly on JBoss 7 AS Created: 15/Apr/13  Updated: 26/Aug/14  Resolved: 19/Jul/13

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: 4.5.10

Type: Bug Priority: Neutral
Reporter: Jaroslav Simak Assignee: Jaroslav Simak
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
relation
is related to DOCU-439 Jboss AS 7 log4j configuration Closed
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Comments   
Comment by Jan Haderka [ 16/May/13 ]

It seems that JBoss 7 automatically adds it's own version of log4j which needs to be excluded for deployments shipped with their own log4j configuration. More info on https://docs.jboss.org/author/display/AS71/How+To?_sscc=t#HowTo-HowdoIuselog4j.propertiesorlog4j.xmlinsteadofusingtheloggingsubsystemconfiguration%3F

Comment by Jan Haderka [ 24/Jul/13 ]

Applying the configuration described in linked article resolves the issue.

Generated at Mon Feb 12 04:00:48 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.