Why do asynchronous EJB3 calls periodically lose their security context on JBoss EAP 6?

Solution In Progress - Updated -

Issue

Why do asynchronous EJB3 calls periodically lose their security context on JBoss EAP 6?

We have a stateless bean that calls an @Asynchronous method in another stateless bean multiple times in order to get better performance. Sometimes it works, but sometimes we get the following exception:

javax.ejb.EJBAccessException: JBAS013323: Invalid User: java.util.concurrent.ExecutionException: javax.ejb.EJBAccessException

It seems as if the asynchronous threads are reused and that the security context is lost somehow.

Our environment looks like the following:

client --> nodeX --- (remoting) --> nodeY (Asyc Method)

Currently we are using JBoss EAP 6.3.3 GA but we also experienced the same behavior in JBoss EAP 6.1.0.GA.

Environment

  • Red Hat JBoss Enterprise Application Platform (EAP)
    • 6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content