Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 2.1.18.Final
Affects Version/s: None
Component/s: None
Labels:
None

Release Note Text:
Undefined
Git Pull Request:
https://github.com/jboss-logging/jboss-logmanager/pull/326, https://github.com/jboss-logging/jboss-logmanager/pull/327, https://github.com/jboss-logging/jboss-logmanager/pull/328

When configuring resources the TCCL should be set to the class loader for the type being configured. In the case of a modular environment the type may use the TCCL to initialize other types. For example in WildFly if a custom-handler is used that handler may be in it's own module and attempt to use the TCCL to initialize another type.

blocks

JBEAP-20766 [GSS](7.3.z) LOGMGR-283 TCCL should be set to logging custom-handler module

Closed

WFCORE-5248 TCCL should be set to logging custom-handler module

Closed

is incorporated by

JBEAP-20918 (7.3.z) Upgrade jboss-logmanager from 2.1.17.Final-redhat-00001 to 2.1.18.Final-redhat-00001

Closed

WFCORE-5259 Upgrade jboss-logmanager to 2.1.18.Final

Closed

is related to

LOGMGR-287 The TCCL needs to be set in additional places when configuring the log manager

Open

Assignee:: James Perkins

Reporter:: James Perkins

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Created:: 2021/01/20 11:35 AM

Updated:: 2024/01/17 6:53 PM

Resolved:: 2021/01/28 2:21 PM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates