[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=13709592#comment-13709592 ] 

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

[~manovotn] I agree that it could be the trouble of the Narayana CDI lookup. There were changes at that code between WFLY 15 and 16 so it's highly possible from that perspective as well.
The code which is used for the lookup is here
https://github.com/jbosstm/narayana/blob/5.9.3.Final/ArjunaJTA/cdi/classes/com/arjuna/ats/jta/cdi/JNDIBean.java#L68
Especially if this is the EAR the classloading is a bit "strange" with this `CDI.current()`. I think we already discussed this aspect for refactoring of the transaction modules in WFLY.
Could be we need some similar handling which is used here https://github.com/jbosstm/narayana/blob/5.9.3.Final/compensations/src/main/java/org/jboss/narayana/compensations/internal/BeanManagerUtil.java ? [~manovotn] do you have some more experience with use of the `CDI.current().lookup` for the EARs?

> [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)