Bug 975559
| Summary: | Handler rollback gets null instance reference if prepare are invoked | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Kyle Lape <klape> |
| Component: | Logging | Assignee: | James Perkins <jperkins> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.1.0 | CC: | cdewolf, jawilson, jperkins, lcosti, myarboro, pkremens, rdickens |
| Target Milestone: | ER4 | Flags: | cdewolf:
needinfo-
|
| Target Release: | EAP 6.1.1 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
In previous versions of JBoss EAP 6, a rollback of a composite operation to remove and re-add an Apache log4j appender would fail if the appender's name was staying the same. The rollback of the composite operation would fail because the reference to the previous log4j appender would have already been removed.
This issue was fixed by not validating whether the reference to the log4j appender exists, as it may be created later.
As a result of this fix, no errors should be seen when a composite operation to remove and re-add an Apache log4j appender is rolled back.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-09-16 20:27:46 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: | |||
| Bug Blocks: | 971618, 975555 | ||
|
Description
Kyle Lape
2013-06-18 18:57:18 UTC
James Perkins <jperkins> updated the status of jira LOGMGR-58 to Resolved James Perkins <jperkins> made a comment on jira LOGMGR-58 Pull request merged Upgrade to logmanager 1.4.3.Final is in ER4. Verified on EAP 6.1.1 ER4 |