[ https://issues.jboss.org/browse/WFLY-11858?page=com.atlassian.jira.plugin... ] Rakesh K. Cherukuri edited comment on WFLY-11858 at 3/18/19 6:38 AM: --------------------------------------------------------------------- Flow: During server startup, Servlet.init() -> SingletonEjbX.serviceMethod -> StatelessEJB.doService() -> SingletonEjbY.performActualService() ^ Interceptor Based on stacktrace, the client call to SingletonEjbY.performActualService() fails as server is not able to construct the component/EJB. The underlying cause is that the CDI unable to find the InitialContext Deployment: EAR ____ WAR ____ lib/<jars-with-ejbs> During startup, only one interceptor is called that makes sure that a transaction is associated (creates a new TX if one is not associated). It uses TransactionSynchronizationRegistry in the process. My two cents: From stack trace its pretty clear that this interceptor has done its job properly as the failure happens between _StatelessEJB.doService() -> SingletonEjbY.performActualService()_ was (Author: rakcheru): Flow: During server startup, Servlet.init() -> SingletonEjbX.serviceMethod -> StatelessEJB.doService() -> SingletonEjbY.performActualService() ^ Interceptor Based on stacktrace, the client call to SingletonEjbY.performActualService() fails as server is not able to construct the component/EJB. The underlying cause is that the CDI unable to find the InitialContext Deployment: EAR -- WAR -- lib/<jars-with-ejbs> During startup, only one interceptor is called that makes sure that a transaction is associated (creates a new TX if one is not associated). It uses TransactionSynchronizationRegistry in the process. My two cents: From stack trace its pretty clear that this interceptor has done its job properly as the failure happens between _StatelessEJB.doService() -> SingletonEjbY.performActualService()_ -- This message was sent by Atlassian Jira (v7.12.1#712002)