[jboss-jira] [JBoss JIRA] (WFLY-10261) @Startup, @WebListener and (@Observes @Initialized(ApplicationScoped.class) are triggered before some components has started

[dbdbdb dbdbdb (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-10261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

dbdbdb dbdbdb updated WFLY-10261:
---------------------------------
    Summary: @Startup, @WebListener and (@Observes @Initialized(ApplicationScoped.class) are triggered before some components has started  (was: @Startup, @WebListener and (@Observes @Initialized(ApplicationScoped.class) are triggered before the container have fully started)


> @Startup, @WebListener and (@Observes @Initialized(ApplicationScoped.class) are triggered before some components has started
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-10261
>                 URL: https://issues.jboss.org/browse/WFLY-10261
>             Project: WildFly
>          Issue Type: Bug
>    Affects Versions: 12.0.0.Final
>            Reporter: dbdbdb dbdbdb
>            Assignee: Jason Greene
>
> We are migrating our applications from Wildfly 10 to Wildfly 12 and sometimes Wildfly 12 trigger {{@Startup (with @PostContruct)}} or {{@WebListener}} or {{(@Observes @Initialized(ApplicationScoped.class)}} before the container have fully started.
> Ex:
> - At these moments we can't inject remote EJBs (simple {{new InitialContext().lookup(jndi)}})
> - Sometimes these {{@Observes}} is fired with null (proxy with null reference) parameter
> {code}
> public void observesContext(@Observes @Initialized(ApplicationScoped.class) ServletContext context){
> 	this.context = context;
> }
> {code}
> *These behavior olny occurs when the server is starting with a application deployed*.
> When the application is deployed after the server is up and running, all goes fine a work.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)