-
Bug
-
Resolution: Done
-
Major
-
None
-
None
The WebDeploymentService in its start/stop lifecycle methods triggers the web application context initialization which can internally trigger various component initialization tasks like startup servlet initializations and servlet context initializations. This currently happens in a MSC thread but instead should be happening via a server executor which is already available for such blocking tasks.
- is related to
-
WFLY-917 jboss-ejb3.xml faults fail silently and result in a hanging thread
- Closed