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

Laird Nelson (Jira) issues at jboss.org
Wed Mar 20 15:23:00 EDT 2019


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

Laird Nelson edited comment on WFLY-11858 at 3/20/19 3:22 PM:
--------------------------------------------------------------

Another possibility for a root cause: should the {{getBeanClass()}} method be overridden in {{JNDIBean}} to return the bean type supplied at construction time?  While reading http://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#selection_ee and http://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#inter_module_injection I am concerned that if {{getBeanClass()}} returns {{AbstractBean$1.class}} or something similar, as it would for the bean that represents {{InitialContext}}, Wildfly might decide that such a class is not visible in the OP's scenario.


was (Author: ljnelson):
Another possibility for a root cause: should the {{getBeanClass()}} method be overridden in {{JNDIBean}} to return the bean type supplied at construction time?  While reading http://docs.jboss.org/cdi/spec/2.0/cdi-spec.html#selection_ee I am concerned that if {{getBeanClass()}} returns {{AbstractBean$1.class}} or something similar, as it would for the bean that represents {{InitialContext}}, Wildfly might decide that such a class is not visible in the OP's scenario.

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


More information about the jboss-jira mailing list