[jboss-jira] [JBoss JIRA] (WFLY-11858) [Wildfly16] CDI fails to inject InitialContext during startup

[Ondra Chaloupka (Jira)]

    [ https://issues.jboss.org/browse/WFLY-11858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13710868#comment-13710868 ] 

Ondra Chaloupka commented on WFLY-11858:
----------------------------------------

[~manovotn] I see. I was investigating a bit and I haven't found the place so far. I tried with weld logging but haven't got any catch. Would you have some clue for me how to get info on all the registered beans (which can be `@Inject`ed?)

To your point about `new IntialContext()` I think it's not an issue as it's practice used on many places in the container and second there should be possibly one `JNDIBean` in container(?, I can be easily missing how the CDI handles this).

> [Wildfly16] CDI fails to inject InitialContext during startup
> -------------------------------------------------------------
>
>                 Key: WFLY-11858
>                 URL: https://issues.jboss.org/browse/WFLY-11858
>             Project: WildFly
>          Issue Type: Bug
>          Components: CDI / Weld, Transactions
>    Affects Versions: 16.0.0.Final
>            Reporter: Rakesh K. Cherukuri
>            Assignee: Matej Novotny
>            Priority: Major
>         Attachments: stacktrace.log
>
>
> We are in the process of upgrading from 14.0.1.Final. While Wildfly 15.0.1 works fine, 16.0.0.Final is intermittently (3 out of 5 times) failing to start with following error
> _WELD-001334: Unsatisfied dependencies for type InitialContext with qualifiers_
> In our application, a bootstrap servlet startsup services (Stateless EJBs) during server startup. During this process the server fails to start with above error.
> Basically CDI is not able to find the appropriate InitialContext bean *intermittently*. This is not failing in our application code but in the wildfly libraries itself.
> Any pointers on this will be helpful. Don't want to end up with startup issues in stage/production :)
> Unfortunately my efforts to come up with a simplified maven module to showcase the error didn't succeed. So, please let me know if any further information is required and i will be glad to fill it in.



--
This message was sent by Atlassian Jira
(v7.12.1#712002)