Bug 1059857
| Summary: | [GSS] (6.3.0) Upgrade log4j-jboss-logmanager changed from 1.0.2.Final-redhat-1 to 1.1.0.Final | |||
|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | James Perkins <jperkins> | |
| Component: | Logging | Assignee: | James Perkins <jperkins> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Nikoleta Hlavickova <nziakova> | |
| Severity: | unspecified | Docs Contact: | Russell Dickenson <rdickens> | |
| Priority: | unspecified | |||
| Version: | 6.3.0 | CC: | a.niemeyer, bmaxwell, brian.stansberry, jdoyle, kkhan, klape | |
| Target Milestone: | DR0 | |||
| Target Release: | EAP 6.3.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1071479 (view as bug list) | Environment: | ||
| Last Closed: | 2014-06-28 15:31:37 UTC | Type: | Component Upgrade | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 1070452, 1088618 | |||
| Bug Blocks: | 1071479 | |||
|
Description
James Perkins
2014-01-30 19:45:26 UTC
Hi, I followed this issue and checked the HEARTBEAT category logging example under OS X and followed the recommendation of replacing the logmanager jar to 1.1.0-Final. Everything works with a log4j.xml, category definitions as well. Today within a windows environment the root logger works so far, but no categories anymore. It seems that something more is broken and leads to an inconsistent behavior between different system enviroments in that 1.1.0-Final. One more thing: the files in the appenders get touched but nothing is written in there, only the root logger writes into the appenders file. Kind regards, Andreas Ok, I got it: replacing the log4j-jboss-logmanager jar is not enough, the need of update the org\jboss\logmanager\main\jboss-logmanager-1.5.2.Final.jar is also required! Verified with EAP 6.3.0 DR0 |