[jboss-jira] [JBoss JIRA] (WFLY-11858) [Wildfly16] CDI fails to inject InitialContext during startup
Ondrej Chaloupka (Jira)
issues at jboss.org
Tue Apr 2 05:02:03 EDT 2019
[ https://issues.jboss.org/browse/WFLY-11858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13716184#comment-13716184 ]
Ondrej Chaloupka commented on WFLY-11858:
-----------------------------------------
[~rakcheru] we already made the release of Narayana `5.9.5.Final` with the fix and the PR for the component in the new version being involved is created for WildFly (WFLY-11917). WildFly release is done quarterly (http://lists.jboss.org/pipermail/wildfly-dev/2017-December/006250.html) and micro releases are done only in case of some blocker issue.
I assume you would need take the WFLY16 and update the Narayana there or wait for the WFLY17 to be released (I expect the WFLY-11917 will be merged till that time).
> [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 Cherukuri
> Assignee: Matěj Novotný
> 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