Loading...

XML

Word

Printable

Type: Component Upgrade
Resolution: Done
Priority: Major
Fix Version/s: 7.2.9.CR1, 7.2.9.GA
Affects Version/s: None
Component/s: Build System, Logging
Labels:
None

CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Target Release:

7.2.z.GA
Git Pull Request:
https://github.com/jbossas/wildfly-core-eap/pull/866

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

Upgrade org.jboss.logmanager:jboss-logmanager to 2.1.15.Final.

Tag: https://github.com/jboss-logging/jboss-logmanager/releases/tag/2.1.15.Final
Diff: https://github.com/jboss-logging/jboss-logmanager/compare/2.1.14.Final...2.1.15.Final
Commit hash: https://github.com/jboss-logging/jboss-logmanager/commit/8b417c5ab9e2d99c3226be8be8a022a0f9b4fe86

clones

JBEAP-19269 [GSS](7.3.z) Upgrade jboss-logmanager from 2.1.14.Final to 2.1.15.Final

Closed

incorporates

LOGMGR-262 When setting the close handlers on a log context the control permission should be checked

Resolved

LOGMGR-263 Logger Lookup is much slower as with JDK 8

Resolved

LOGMGR-260 System loggers run with level ALL

Resolved

JBEAP-18947 [GSS](7.2.z) LOGMGR-263 - Logger Lookup is much slower as with JDK 8

Closed

is incorporated by

JBEAP-19271 (7.2.z) Upgrade WildFly Core from 6.0.27.Final-redhat-00001 to 6.0.28.Final-redhat-00001

Closed

(1 is incorporated by)

Assignee:: Ilia Vassilev

Reporter:: James Perkins

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: 2020/04/16 1:36 PM

Updated:: 2021/10/24 6:42 AM

Resolved:: 2020/06/08 2:51 AM