Hi Romain, We are using few async servlets so that when the request comes, it will be processed by another thread from thread pool.It is working fine. but, security context is not being propagated to EJB. We are always getting principal name as guest from EJBContext. We do authentication suing request.login().
I do agree that it is not recommended to create custom threads inside container since context is not propagated properly. Java EE work managers are intended to solve this issue. I tried with CommonJ WorkManger and Execututor Service in TomEE. Still, security context is not being propagated. Can you please advise? Thanks & Regards, Srinivas Atluri. -- View this message in context: http://tomee-openejb.979440.n4.nabble.com/TomEE-security-context-is-not-getting-propagated-with-WorkManagers-tp4677483.html Sent from the TomEE Dev mailing list archive at Nabble.com.
