Bug 1050068
| Summary: | [GSS] (6.2.x) Using directory grouping by-type results in the wrong logging.properties file being used | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | James Perkins <jperkins> |
| Component: | Domain Management | Assignee: | Carlo de Wolf <cdewolf> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Petr Kremensky <pkremens> |
| Severity: | medium | Docs Contact: | Russell Dickenson <rdickens> |
| Priority: | unspecified | ||
| Version: | 6.2.0 | CC: | bmaxwell, cdewolf, emuckenh, jawilson, kkhan, lcosti, myarboro, nziakova, smumford |
| Target Milestone: | CR1 | ||
| Target Release: | EAP 6.2.1 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
When defining servers with directory-grouping="by-type" the domain/configuration/logging.properties file was always used, which was the incorrect configuration. This error resulted in the wrong logging settings being used. The cause was faulty logic by which the properties file was selected was incorrect. To resolve this problem, the logic by which the properties file was selected has been improved and the correct logging.properties file is now used when directory-grouping="by-type" is used.
|
Story Points: | --- |
| Clone Of: | 1031129 | Environment: | |
| Last Closed: | 2014-02-24 20:13:55 UTC | Type: | Bug |
| 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: | 1031129 | ||
| Bug Blocks: | 1027004 | ||
|
Description
James Perkins
2014-01-08 16:49:27 UTC
Marking for inclusion in 6.2.1 release notes. Verified with 6.2.1.CP.CR1-patch. Set 'Version' field to ensure this ticket appears in documentation effort dashboards. Hey Carlo. Can I get some more info on what was causing this bug and how it was resolved? Any help is greatly appreciated. Marking as incomplete release note for 6.2.1. In the absence of SME input, I have completed this ticket's release notes entry based on the comments in the ticket's history, also the associated pull request. |