Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 7.4.1.CR1, 7.4.1.GA
Affects Version/s: None
Component/s: Management
Labels:
- downstream_dependency
- test_included

Blocked:
False
Ready:
False
CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
QE Test Coverage:
+
Release Note Text:
Undefined
Target Release:

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

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

If an operation fails during boot, the (Abstract)OperationContext reports that to the BootErrorCollector.

But it's possible for non-boot operations to execute during boot. These shouldn't be external requests (which get rejected before they get to the point of running with an OperationContext) but java agents run in-vm and can invoke operations. I believe Dynatrace may do that kind of thing.

We should try and distinguish the OperationContexts that are actually executing the boot steps from those that are just running during boot.

Whoever works on this needs to fully understand boot and the various types of operation contexts, including understanding how parallel boot works.

clones

WFCORE-5368 Populating the boot error collector does not distinguish between problems that happen as part of boot vs those that happen during boot

Resolved

is cloned by

JBEAP-21845 [GSS](7.3.z) WFCORE-5368 - Populating the boot error collector does not distinguish between problems that happen as part of boot vs those that happen during boot

Closed

is incorporated by

JBEAP-21978 (7.4.z) Upgrade WildFly Core from 15.0.2.Final-redhat-00001 to 15.0.3.Final-redhat-00001

Closed

links to

KCS

Assignee:: Brian Stansberry

Reporter:: Brian Stansberry

Votes:: 0 Vote for this issue

Watchers:: 11 Start watching this issue

Created:: 2021/05/06 2:36 PM

Updated:: 2024/10/01 8:43 PM

Resolved:: 2021/07/22 8:03 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates