[jboss-jira] [JBoss JIRA] (WFLY-11601) Weld vs Undertow bootstrap: Race condition

[ https://issues.jboss.org/browse/WFLY-11601?page=com.atlassian.jira.plugin... ] Matěj Novotný edited comment on WFLY-11601 at 6/5/19 7:17 AM: -------------------------------------------------------------- bq. If the flag is false, we catch the ServletContext and fire the event as soon as endInitialization completes - just like it is done for non-web modules. Non-web modules are handled differently because Weld alone knows when to fire that event. In order to know when do it for web modules, we need the mechanism that we use now - for undertow to tell us basically. bq. I had no time to investigate it myself but why is the BeanDeploymentModules.processBeanDeployments executed after the cleanup code? Not sure from the top of my head, playing with it yesterday I tried swapping the two and it still worked. That's why i suggested splitting the two in separate invocations. But I assume some other events (in EE server bootstrap) might be waiting on that and Weld doesn't want to look fully booted when it is effectively not since the cleanup wasn't performed. bq. Does it require a spec change? Spec doesn't do any of the optimizations we have here. Also, going that way drastically delays any actual solution so I'd say we first seek a solution to a Weld-specific bootstrap which, after all, is what all integrators rely on anyway. was (Author: manovotn): bq. If the flag is false, we catch the ServletContext and fire the event as soon as endInitialization completes - just like it is done for non-web modules. Non-web modules are handled differently because Weld alone knows when to fire that event. In order to know when do it for web modules, we need the mechanism that we use now - for undertow to tell us basically. bq . I had no time to investigate it myself but why is the BeanDeploymentModules.processBeanDeployments executed after the cleanup code? Not sure from the top of my head, playing with it yesterday I tried swapping the two and it still worked. That's why i suggested splitting the two in separate invocations. But I assume some other events (in EE server bootstrap) might be waiting on that and Weld doesn't want to look fully booted when it is effectively not since the cleanup wasn't performed. bq. Does it require a spec change? Spec doesn't do any of the optimizations we have here. Also, going that way drastically delays any actual solution so I'd say we first seek a solution to a Weld-specific bootstrap which, after all, is what all integrators rely on anyway. -- This message was sent by Atlassian Jira (v7.12.1#712002)