Hi to all,

reading new Servlet 3.0 specifications, I found startAsynch method for HttpServletRequest, which claims to make things in asynchronous way propagating the right contextual information to the passed runnable.

I wrote this code inside doGet method of my servlet:

@EjB
private EJBManager manager;

protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException {
     if(request.getUserPrincipal() != null && request.isUserInRole("admin"))
          //Method protected by @RolesAllowes("admin") annotation EJB-side
          manager.verify();

     final AsyncContext ctx = request.startAsync(request,response);
     ctx.start(new Runnable(){
          HttpServletRequest = (HttpServletRequest)ctx.getRequest();
          if(request.getUserPrincipal() != null && request.isUserInRole("admin"))
               //Method protected by @RolesAllowes("admin") annotation EJB-side
               manager.verify();
     });
}

When calling manager.verify() the first time, outside AsyncContext everything works fine, but when entering inside the Runnable in debug, i can see that, even the 'if' is succesfully passed (so the principal has been correctly propagated to the Runnable in AsyncContext), when calling the EJB method protected by the @RolesAllowed annotation, JBoss throws an exception saying that "The invocation of method verify" is not allowed.

Can anyone help me?

Platform: JBoss EAP 6.2.0

EDIT: Same behavior in JBoss EAP 6.3.0