-
Bug
-
Resolution: Done
-
Major
-
None
The module org.jboss.as.domain-http-error-context.eap is not present when provisioning EAP with galleon layers. This create the following ERROR trace at startup:
9:37:51,077 ERROR [org.jboss.as.domain.http.api.undertow] (MSC service thread 1-2) WFLYDMHTTP0004: Unable to load error context for slot eap, disabling error context.
The problem occurs when the galleon layer "management" (or any layer that depends on it) is provisioned. The module org.jboss.as.domain-http-error-context.main is provisioned but not the org.jboss.as.domain-http-error-context.eap
This package needs to be explicitly provisioned.
A possibility would be by redefining the "management" layer in ee-galleon-pack and references this package (optional dependency).
This change would have to be done in EAP code base, not in WildFly, WildFly is not impacted by this problem.
NB: This impacts Bootable jar for EAP that relies on Galleon layers to provision the server.
- is cloned by
-
JBEAP-19748 (7.3.z) domain-http-error-context.eap not provisioned with Galleon
- Closed
- is related to
-
JBEAP-19950 Eliminate use of separate 'eap' module slot for web content
- Closed