[
https://issues.jboss.org/browse/WFLY-11858?page=com.atlassian.jira.plugin...
]
Matej Novotny edited comment on WFLY-11858 at 3/18/19 4:27 AM:
---------------------------------------------------------------
Hi [~rakcheru]
Can you please draft what does your application look like? Are we talking WAR or EAR?
What do your beans looks like and what functionality they use to trigger this behaviour?
What interceptors you have there? Any transactional behaviour (see below)?
I know you are saying that the error comes up in WFLY libraries but I suppose that's
still triggered by something in your code because otherwise this would show up in many
tests WFLY has.
[~ochaloup] I suspect Narayana's deps here. In the stacktrace, the actual bean that
tries to grab {{InitialContext}} is
[{{JNDIBean}}|https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/cdi/classes/com/arjuna/ats/jta/cdi/JNDIBean.java#L68].
I am guessing that based on this log line:
bq. {{at org.jboss.jts//com.arjuna.ats.jta.cdi.JNDIBean.create(JNDIBean.java:68)}}
Might be something to do with how WFLY services boot up or rather in what order? Hard to
tell without reproducer...
was (Author: manovotn):
Hi [~rakcheru]
Can you please draft what does your application look like? Are we talking WAR or EAR?
What do your beans looks like and what functionality they use to trigger this behaviour?
What interceptors you have there? Any transactional behaviour (see below)?
I know you are saying that the error comes up in WFLY libraries but I suppose that's
still triggered by something in your code because otherwise this would show up in many
tests WFLY has.
[~ochaloup] I suspect Narayana's deps here. In the stacktrace, the actual bean that
tries to grab {{InitialContext}} is
[{{JNDIBean}}|https://github.com/jbosstm/narayana/blob/master/ArjunaJTA/cdi/classes/com/arjuna/ats/jta/cdi/JNDIBean.java#L68].
I am guessing that based on this log line:
bq. {{at org.jboss.jts//com.arjuna.ats.jta.cdi.JNDIBean.create(JNDIBean.java:68)}}
[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
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)