Bug 1148632 - Upgrade log4j-jboss-logmanager from 1.1.0.Final-redhat-2 to 1.1.1.Final
Summary: Upgrade log4j-jboss-logmanager from 1.1.0.Final-redhat-2 to 1.1.1.Final
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Logging
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: DR4
: EAP 6.4.0
Assignee: James Perkins
QA Contact: Nikoleta Hlavickova
URL:
Whiteboard:
Depends On:
Blocks: 1079106
TreeView+ depends on / blocked
 
Reported: 2014-10-01 23:22 UTC by James Perkins
Modified: 2019-08-19 12:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-19 12:42:59 UTC
Type: Component Upgrade
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1195950 0 unspecified CLOSED RHEL6 RPMs: Upgrade log4j-jboss-logmanager to 1.1.1.Final-redhat-1 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1195951 0 unspecified CLOSED RHEL5 RPMs: Upgrade log4j-jboss-logmanager to 1.1.1.Final-redhat-1 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1195952 0 unspecified CLOSED RHEL7 RPMs: Upgrade log4j-jboss-logmanager to 1.1.1.Final-redhat-1 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker WFCORE-138 0 Major Resolved Upgrade log4j-jboss-logmanager from 1.1.0.Final to 1.1.1.Final 2020-04-24 11:15:44 UTC

Internal Links: 1195950 1195951 1195952

Description James Perkins 2014-10-01 23:22:34 UTC
Contains fixes for running in a security manager and returning the correct logger name for Logger.getParent().

Comment 2 Nikoleta Hlavickova 2014-10-21 09:22:12 UTC
Verified with EAP 6.4.0.DR6


Note You need to log in before you can comment on or make changes to this bug.