JBoss AS 7.1.1 does not longer honoring Log4j level settings
Description
causes
duplicates
relates
Activity
Show:
Michael Saechang May 23, 2012 at 12:45 PM
Committed on:
Portal 6.1.x CE GIT ID: 1a7fd537c3ca16723196dba113c6ff51cb92c9a9.
Portal 6.2.x GIT ID: 9fee66a039b348d1ebe39efb0e3e3e0c3d1f584e.
Igor Spasic May 18, 2012 at 2:20 AM
However, logs will look a bit odd:
Fixed
Details
Assignee
Michael SaechangMichael Saechang(Deactivated)Reporter
Igor SpasicIgor Spasic(Deactivated)Branch Version/s
6.1.xBackported to Branch
CommittedEpic/Theme
Git Pull Request
Components
Affects versions
Priority
Medium
Details
Details
Assignee
Michael SaechangReporter
Igor SpasicBranch Version/s
6.1.x
Backported to Branch
Committed
Epic/Theme
Git Pull Request
Components
Affects versions
Priority
MediumZendesk Support
Linked Tickets
Zendesk Support
Linked Tickets
Zendesk Support
Linked Tickets
Created May 18, 2012 at 2:04 AM
Updated June 24, 2023 at 4:00 PM
Resolved May 18, 2012 at 9:05 AM
It seems like Log4j has been promoted to a system module, so now it has the priority against portal jars, without declaring anything, by default.
The workaround is to exclude the module from jboss deployment.
This will be fixed in jboss 7.1.2: https://issues.jboss.org/browse/AS7-514