Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Critical
Fix Version/s: 7.3.7.CR1, 7.3.7.GA
Affects Version/s: 7.3.x
Component/s: Logging
Labels:
None

Blocked:
False
Ready:
False
Bugzilla References:
https://issues.redhat.com/browse/EAP7-1481
CDW devel_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Release Note Text:
Undefined
Target Release:

7.3.z.GA
Git Pull Request:
https://github.com/jbossas/wildfly-core-eap/pull/1010
Market:

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

Basically the customer is hitting an issue where the log manager is on the boot class path and cannot use customer log handlers (https://issues.redhat.com/browse/WFCORE-4674)

As it turns out, thigh might be fixed by exposing the ability to add jboss-modules specific arguments

is incorporated by

JBEAP-21351 (7.3.z) Upgrade WildFly Core from 10.1.19.Final-redhat-00001 to 10.1.20.Final-redhat-00001

Closed

is related to

WFCORE-4674 Custom handlers, formatters and filters cause the server to crash if the log manager is on the boot class path

Closed

CLOUD-3537 Update startup module / agent loading to not require bootclasspath/a

New

MODULES-393 Make jboss-modules a Java agent and allow other agents to be set as module arguments

Resolved

JBEAP-20502 (7.3.z) Upgrade JBoss Modules from 1.10.0.Final to 1.11.0.Final

Closed

Assignee:: James Perkins

Reporter:: Francesco Marchioni (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 8 Start watching this issue

Created:: 2021/03/26 12:58 PM

Updated:: 2024/08/27 1:53 PM

Resolved:: 2021/03/29 11:02 AM